It’s not easy to make it so that editing the config preserves the existing formatting and comments in the config files, but that doesn’t mean it shouldn’t be done.The CLI would need a new option to tell npm config to modify the per-package configuration, but beyond that, the existing code should make it pretty clear how to add the new type of editing. npm config set and npm config set -g only allow you to edit two of those four kinds of files I agree that if npm is going to support per-package configuration, it should be configurable via the CLI. npmrc at ”$(pwd)/.npmrc”, a per-user file at ”$HOME/.npmrc” (what calls “the global config”), a global file installed at ”$(npm -g prefix)/etc/npmrc”, and a special “ npmrc” bundled into the CLI package itself (used to ensure that things stay installed in the correct places on Windows). npmrc files evaluated by npm's configuration framework: a per-package. There are actually four different kinds of.There's even more going on in this issue than there appears at first:
0 kommentar(er)
