Bundled dependencies for [email protected] have versions of libnpmexec, libnpmpack, libnpmversion which do not match package.json

[dominykas]

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

Current Behavior

npm ls -g --all results in:

06:03:17 #25 8.386 npm error invalid: [email protected] /usr/local/lib/node_modules/npm/node_modules/libnpmexec
06:03:17 #25 8.386 npm error invalid: [email protected] /usr/local/lib/node_modules/npm/node_modules/libnpmpack
06:03:17 #25 8.386 npm error invalid: [email protected] /usr/local/lib/node_modules/npm/node_modules/libnpmversion

Expected Behavior

No errors.

Steps To Reproduce

1. Tested inside Ubuntu@22 docker container and on macOS with [email protected] with baseline [email protected]
2. Run npm i -g npm

Downloading the latest npm tarball via npm pack npm highlights the problem:

~/devel/experiments
❯ cat package/package.json | grep libnpmexec
    "libnpmexec": "^7.0.4",
    "libnpmexec",

~/devel/experiments
❯ cat package/node_modules/libnpmexec/package.json| grep version
  "version": "8.0.0",

Environment

• npm:
• Node.js:
• OS Name:
• System Model Name:
• npm config:

; copy and paste output from `npm config ls` here

[wraithgar]

Looks like the release script isn't bumping the base package.json anymore. This is mostly a cosmetic problem, as npm bundles all of its dependencies.