pnpm install multiple bindings of different libc

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

I can confirm this behaviour as we're experiencing the same as described in this issue.

Our package.json contains the following configuration:

{
  "name": "sharp-binaries",
  "version": "1.0.0",
  "description": "",
  "main": "index.js",
  "scripts": {},
  "dependencies": {
    "express": "4.18.2",
    "sharp": "0.33.0"
  },
  "pnpm": {
    "supportedArchitectures": {
      "os": ["linux"],
      "cpu": ["x64"],
      "libc": ["musl"]
    }
  }
}

We're building with Docker:

FROM node:lts-alpine3.18
WORKDIR /app
RUN corepack enable && corepack prepare pnpm@latest --activate
COPY package*.json ./
RUN pnpm i

docker build . --no-cache --platform=linux/amd64 --tag 'sharp-binaries:latest'

After building, we're seeing both linux-x64 and linuxmusl-x64 packages:

@zkochan

The documentation doesn't tell much about how this is supposed to work.

Is this supposed to work with transitive optional dependencies, @zkochan?

I think the problem is that pnpm is flagging every libc as any, for example

checkPlatform: registry.npmjs.org/@img/sharp-linux-x64/0.33.0 is installable {
  wantedPlatform: { cpu: [ 'x64' ], os: [ 'linux' ], libc: [ 'any' ] },
  current: { os: [ 'linux' ], cpu: [ 'x64' ], libc: [ 'musl' ] }
}

I'm checking it

@nachoaldamav

@nachoaldamav I am having the same issue with @swc/core wich install both @next/swc-linux-x64-gnu and @next/swc-linux-x64-musl. I would like to clarify, this issue is caused by the missing libc field in package metadata provided by npm registry? If so, the issue will not be fixed until the npm registry starts filling this value?

@c0m1c5an5

@c0m1c5an5 Yes, but there is an option to fix it in pnpm itself, but we would need to fetch the whole manifests in order to make it work. Right now pnpm fetches the simplified manifests that includes the os and cpu but not the libc.

fix: install packages with incompatible libc

fix: install packages with incompatible libc (pnpm#8569)

chore(deps): update pnpm to v9.12.0

This seems to have popped up again, I'm using 10.8.0 and the same reproduction steps above work for me. I've also tried a couple of 9.15.x versions and have been able to reproduce there as well.

I traced through some of the pnpm code and it seems as though the PackageManifest object returned from the npm registry is not including the libc field.

fix(docker): Prune wrong-libc native bindings around a pnpm bug

Navigation Menu

Repository navigation

pnpm install multiple bindings of different libc #7362

Verify latest release

pnpm version

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

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

Reproduction steps

Describe the Bug

Expected Behavior

Which Node.js version are you using?

Which operating systems have you used?

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

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

pnpm install multiple bindings of different libc #7362

Description

Verify latest release

pnpm version

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

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

Reproduction steps

Describe the Bug

Expected Behavior

Which Node.js version are you using?

Which operating systems have you used?

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

Activity

adriaanmeuris commented on Nov 30, 2023

KSXGitHub commented on Dec 4, 2023

nachoaldamav commented on Dec 5, 2023

c0m1c5an5 commented on Feb 29, 2024

nachoaldamav commented on Feb 29, 2024

KSXGitHub commented on Sep 25, 2024

mrstork commented on Apr 10, 2025

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions