Skip to content

Bundled dependencies for npm@10.6.0 have versions of libnpmexec, libnpmpack, libnpmversion which do not match package.json #7423

@dominykas

Description

@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: libnpmexec@8.0.0 /usr/local/lib/node_modules/npm/node_modules/libnpmexec
06:03:17 #25 8.386 npm error invalid: libnpmpack@7.0.0 /usr/local/lib/node_modules/npm/node_modules/libnpmpack
06:03:17 #25 8.386 npm error invalid: libnpmversion@6.0.0 /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 Node@20.12.2 with baseline npm@10.5.0
  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

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      pFad - Phonifier reborn

      Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

      Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


      Alternative Proxies:

      Alternative Proxy

      pFad Proxy

      pFad v3 Proxy

      pFad v4 Proxy