The target file is rewritten as a whole, anycodings_npm in the course of which any comments anycodings_npm (#-prefixed lines) in the original file anycodings_npm are lost (but all key-value pairs are anycodings_npm preserved). Npm config set script-shell pwsh -userconfig. npm gets its configuration values from the following sources, sorted by priority: Command Line Flags Putting -foo bar on the command line sets the foo. When used with the -json flag, it can set both simple and complex configuration settings, including Arrays and Objects. When used without the -json flag, it can only set a simple configuration setting (a string, a number, or a boolean). npmrc file via anycodings_npm -userconfig: # Updates. This command will set a configuration setting. npmrc file.Į.g., from a given project's root anycodings_npm folder, the following command anycodings_npm project-locally configures pwsh anycodings_npm (PowerShell Core) as the shell to run anycodings_npm scripts with, by making npm config anycodings_npm operate on the local.

Default: user unless -global is passed, which will also set this value to global. The project config file is loaded based on the local prefix (which can only be set by the CLI config options, and otherwise defaults to a walk up the folder. It's a bit awkward, but if your npm anycodings_npm version is recent enough, you can anycodings_npm repurpose the -userconfig option to anycodings_npm make npm config operate on a anycodings_npm project-specific. 2 days ago The command to run for npm edit and npm config edit.

It is baffling that this is seemingly anycodings_npm still not directly supported as of npm anycodings_npm v6.9.0.

Npm config set for project