Skip to content

pnpm install multiple bindings of different libc #7362

@Timeless0911

Description

@Timeless0911

Verify latest release

  • I verified that the issue exists in the latest pnpm release

pnpm version

latest

Which area(s) of pnpm are affected? (leave empty if unsure)

No response

Link to the code that reproduces this issue or a replay of the bug

No response

Reproduction steps

Just init an empty package.json as follows

{
  "name": "pnpm",
  "version": "1.0.0",
  "description": "",
  "main": "index.js",
  "scripts": {
    "test": "echo \"Error: no test specified\" && exit 1"
  },
  "author": "",
  "license": "ISC",
  "devDependencies": {
    "@rspack/binding": "latest"
  },
  "pnpm": {
    "supportedArchitectures": {
      "os": [
        "linux"
      ],
      "cpu": [
        "x64"
      ],
      "libc": [
        "glibc"
      ]
    }
  }
}

Describe the Bug

Run pnpm install, you will find both binding-linux-x64-gnu and binding-linux-x64-musl in .pnpm folder.

Expected Behavior

only one of binding-linux-x64-gnu and binding-linux-x64-musl will be installed according to the libc env.

Which Node.js version are you using?

18.17.1

Which operating systems have you used?

  • macOS
  • Windows
  • Linux

If your OS is a Linux based, which one it is? (Include the version if relevant)

No response

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions