Release v9.0.0-pre.6 · npm/cli

9.0.0-pre.6 (2022-10-19)

npm now outputs some json errors on stdout. Previously npm would output all json formatted errors on stderr, making it difficult to parse as the stderr stream usually has logs already written to it. In the future, npm will differentiate between errors and crashes. Errors, such as E404 and ERESOLVE, will be handled and will continue to be output on stdout. In the case of a crash, npm will log the error as usual but will not attempt to display it as json, even in --json mode. Moving a case from the category of an error to a crash will not be considered a breaking change. For more information see npm/rfcs#482.
npm config set will no longer accept deprecated or invalid config options.
timing and loglevel changes
- timing has been removed as a value for --loglevel
- --timing will show timing information regardless of
  --loglevel, except when --silent
deprecate boolean install flags in favor of --install-strategy
- deprecate --global-style, --global now sets --install-strategy=shallow
- deprecate --legacy-bundling, now sets --install-strategy=nested
npm will no longer attempt to modify ownership of files it creates
this package no longer attempts to change file ownership automatically
this package no longer attempts to change file ownership automatically

d3543e9 output json formatted errors on stdout (#5716) (@lukekarrys)
be642c6 refuse to set deprecated/invalid config (#5719) (@wraithgar)
332914b separate configs for --timing and --loglevel (@lukekarrys)
f653785 deprecated key, cert config options and updated registry scoped auth docs (@fritzy)
de2d33f add --install-strategy=hoisted|nested|shallow, deprecate --global-style, --legacy-bundling (#5709) (@fritzy)
58065bc #5704 do not alter file ownership (@nlf)
475e9b6 #5703 do not alter file ownership (@nlf)