Packages

@npmcli/arborist

10.0.5 · 18 Nov 2026ISC9.7M / weekRepositoryHomepagenpmAtom feed

Your version

9.0.0

major16 Dec 2024Where it was published

9.9.4 is the newest release of 9.x.

In short

17 breaking3 deprecated22 new8 fixed3 changed47 internal

  • Breaking

    npm is now compatible with the following semver range for node: ^14.17.0 || ^16.13.0 || >=18.0.0

  • Breaking

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

  • Breaking

    The presence of auth related settings that are not scoped to a specific registry found in a config file is no longer supported and will throw errors

  • Breaking

    login, adduser, and auth-type changes

  • Breaking

    npm pack now follows a strict order of operations when applying ignore rules. If a files array is present in the package.json, then rules in .gitignore and .npmignore files from the root will be ignored.

  • Breaking

    Links generated from git urls will now use HEAD instead of master as the default ref

  • Breaking

    timing and loglevel changes

  • Breaking

    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.

Release note

Breaking changes

  • Breaking

    npm is now compatible with the following semver range for node: ^14.17.0 || ^16.13.0 || >=18.0.0

  • Breaking

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

  • Breaking

    The presence of auth related settings that are not scoped to a specific registry found in a config file is no longer supported and will throw errors

  • Breaking

    login, adduser, and auth-type changes

    • legacy auth types sso, saml & legacy have been consolidated into "legacy"

    • auth-type defaults to "web"

    • login and adduser are now separate commands that send different data to
      the registry.

    • auth-type config values web and legacy only try
      their respective methods, npm no longer tries them all and waits to see
      which one doesn't fail.

  • Breaking

    npm pack now follows a strict order of operations when applying ignore rules. If a files array is present in the package.json, then rules in .gitignore and .npmignore files from the root will be ignored.

  • Breaking

    Links generated from git urls will now use HEAD instead of master as the default ref

  • Breaking

    timing and loglevel changes

    • timing has been removed as a value for --loglevel

    • --timing will show timing information regardless of
      --loglevel, except when --silent

  • Breaking

    --timing file changes:

    • When run with the --timing flag, npm now writes timing data to a
      file alongside the debug log data, respecting the logs-dir option and
      falling back to <CACHE>/_logs/ dir, instead of directly inside the
      cache directory.

    • The timing file data is no longer newline delimited JSON, and instead
      each run will create a uniquely named <ID>-timing.json file, with the
      <ID> portion being the same as the debug log.

    • Finally, the data inside the file now has three top level keys,
      metadata, timers, and unfinishedTimers instead of everything being
      a top level key.

  • Breaking

    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.

  • Deprecated

    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

  • Breaking

    npm config set will no longer accept deprecated or invalid config options

  • Breaking

    install-links config defaults to "true"

  • Breaking

    node-version config has been removed

  • Breaking

    npm-version config has been removed

  • Breaking

    npm access subcommands have been renamed

  • Breaking

    npm birthday has been removed

  • Breaking

    npm set-script has been removed

  • Breaking

    npm bin has been removed (use npx or npm exec to execute binaries)

Features

  • Introduce the npm config fix command

  • Explicitly validate config within the cli

  • rewrite: Docs generation

  • Use v3 lockfiles by default

  • Implement new npm-packlist behavior

  • Write eresolve error files to the logs directory

  • Timings are now written alongside debug log files

  • Default auth-type to "web"

  • query: Display queryContext in results

  • Separate login/adduser & remove unnecessary auth types

  • rewrite: npm access

  • rewrite: libnpmaccess

  • workspaces: Update supported node engines in package.json

  • Deprecated

    Add --install-strategy=hoisted|nested|shallow, deprecate --global-style, --legacy-bundling

  • Remove npm birthday

  • Remove npm set-script

  • Default install-links to "true"

  • Remove npm bin

  • Update supported node engines in package.json

  • Output json formatted errors on stdout

  • Refuse to set deprecated/invalid config

  • Separate configs for --timing and --loglevel

  • Deprecated

    Deprecated key, cert config options and updated registry scoped auth docs

Bug Fixes

  • Add tag to publish log message

  • config: Remove node-version and npm-version

  • libnpmpack: Obey foregroundScripts

  • npm link should override --install-links

  • Ensure Arborist constructor gets passed around everywhere for pacote

  • audit: Add a condition to allow third-party registries returning E400 (@juanheyns, Juan Heyns)

  • Attempt more graceful failure in older node versions

  • npm hook ls duplicates hook name prefixes

  • Account for new npm-package-arg behavior

  • Remove chownr and mkdirp-infer-owner

Dependencies

df77a1f #5707 Update Major Versions of Dependencies

Removed

A whole project to check? Paste its package.json in the dependency check: every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.