[BUG] node-config package.json has not all the parsers available installed as production dependencies about node-config HOT 6 CLOSED

If we installed all the parsers in production, that would only bloat the disk space and memory use in production.

I run more than a hundred node apps on the same server in production which all use Node config. How many memory they use matters-- memory is one of the primary things I'm paying to rent.

So, no, I won't want to pay for extra memory to keep the YAML parser in memory or on disk if I don't need it.

from node-config.

Thank you for the question Flavio and for your answer, Mark. It highlights one of the most valuable features of node-config, the one that keeps it as relevant in 2024 as it was when first published in 2011.

Use the parser you want, and don't bring in what you don't need.

This module has stood the test of time because of this feature. Today, users aren't bogged down with outdated dependencies with maintenance and security issues. Tomorrow, your modules will still pass security audits and stay trim as new parsers become available.

In the not too distant future, that most popular voice-file configuration format will be all the rage. The voice-file-parser will have matured and all the latest projects use it. The newer thought-wave file format will be used by a small number of apps, and extensions will allow comments (they'll be called commentary) embedded as voice-file sections. And node-config will work with all of it.

... and of course your application will still be trim, secure, and running. You'll be able to spin yarns with your grandkids about having to hand craft those configurations in a format we used to call eeeyaaaaaaaaaaaaaaaml.

from node-config.

The YAML dependency is optional and you didn't add it to your package.json, and you got a clear error message explaining what the problem was and how to fix it. That's not a bug in node-config.

from node-config.

Thanks! I was talking about de dependencies of the project. When I install it as production the node-config has just the json parser as production dependency

from node-config.

from node-config.

from node-config.