BREAKING CHANGE: this package no longer attempts to change file ownership automatically

BREAKING CHANGE: this package no longer attempts to change file ownership automatically

@npmcli/[email protected]

- @npmcli/[email protected]
- @npmcli/[email protected]
- @npmcli/[email protected]
- @npmcli/[email protected]
- @npmcli/[email protected]
- @npmcli/[email protected]
- @npmcli/[email protected]
- @npmcli/[email protected]
- @npmcli/[email protected]
- @npmcli/[email protected]
- @npmcli/[email protected]
- @npmcli/[email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]

Removed dependencies:
- `@npmcli/fs`

closes npm/statusboard#540

BREAKING CHANGE: npm will no longer attempt to modify ownership of files it creates

…al-style, --legacy-bundling (#5709)

BREAKING CHANGE: 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`, `npm@`, and `npm@*` are all now the same spec

…oped auth docs

I manually installed `@npmcli/fs` and `minipass-fetch` to the root of
our the dependency tree so that the deduped version would now live at
the root of `node_modules/` and any conflicting versions would be deduped
inside of its nested parent `node_modules/` directory. Once this was
locked in `package-lock.json` removing them from the `package.json` does
not undo the hoisting and deduping.

This has no effect on the resolved versions bundled with `npm` but it
does make it easier to visually scan the output of `query` commands to
be sure we are not inadvertently deduping dependencies in the future.

BREAKING CHANGE: `timing` and `loglevel` changes
- `timing` has been removed as a value for `--loglevel`
- `--timing` will show timing information regardless of
  `--loglevel`, except when `--silent`

Closes npm/statusboard#455
Closes npm/statusboard#454

Previously, `npmlog` was attempting to enable the progress bar even when
logs were paused. This displayed the most recent log (most often an
error) for the rest of the process.

Fixes #4527

* fix: duplicate hook names

* fix: incorrect names in mocks

BREAKING CHANGE: `npm config set` will no longer accept deprecated or
invalid config options.

This also adds a new output method `outputBuffer()` which will buffer
all output until it is flushed in the exit handler. This allows the exit
handler to catch any errors and append them to the output when in json
mode. This was necessary to not introduce a regression in the case of
#2150.

BREAKING CHANGE: `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.

Closes #2740
Closes npm/statusboard#589

Co-authored-by: Luke Karrys <[email protected]>