Skip to content

[BUG] install-strategy=linked: a fresh install reports "up to date" instead of "added N" #9623

Closed

Description

@manzoorwanijk

Part of #9608.

Is there an existing issue for this?

  • I have searched the existing issues

This issue exists in the latest npm version

  • I am using the latest npm

This is not just a request to bump a dependency for a CVE

  • This is not solely a request to bump a dependency for a CVE

Current Behavior

A fresh npm install under install-strategy=linked that actually creates the .store entries and symlinks prints up to date, audited N packages instead of added N packages. The packages are installed correctly; only the summary line is misleading, which can lead users and CI to believe nothing changed. The hoisted strategy prints added N packages.

Expected Behavior

A fresh install that materializes packages should report the number of packages added (e.g. added N packages) under the linked strategy, matching the hoisted strategy.

Steps To Reproduce

cd "$(mktemp -d)"
echo 'install-strategy=linked' > .npmrc
echo '{ "name": "cq", "version": "1.0.0", "dependencies": { "minimatch": "3.0.4" } }' > package.json
npm install
#   linked:  up to date, audited 5 packages          (it just created 4 store entries + a symlink)
#   hoisted: added 4 packages, and audited 5 packages

Environment

  • npm: 12.0.0-pre.1 (latest)
  • Node.js: v24.17.0
  • OS Name: macOS (Darwin 25.5.0)
  • System Model Name: MacBook (arm64)
  • npm config:
install-strategy=linked

Activity

  1. added a commit that references this issue on Jun 25, 2026
    0c33947
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions