bitwarden-cli: No native build was found for platform=linux arch=x64 runtime=node abi=115 uv=1 libc=glibc node=20.18.3

[devurandom]

Nixpkgs version

• Unstable (25.05)

Describe the bug

Any operation that involves unlocking the Bitwarden Vault with the "master" password (bw unlock, bw list items --search ...) fails with:

No native build was found for platform=linux arch=x64 runtime=node abi=115 uv=1 libc=glibc node=20.18.3
    loaded from: /nix/store/cyzz8f0yissb3gdkc8181h8db1lpil25-bitwarden-cli-2025.1.3/lib/node_modules/@bitwarden/clients/node_modules/argon2

Steps to reproduce

On a system with:

  environment.systemPackages = (with pkgs; [
    bitwarden-cli
  ];

Where you ran bw login before and where bw unlock used to work, run:

❯ bw unlock
? Master password: [hidden]
No native build was found for platform=linux arch=x64 runtime=node abi=115 uv=1 libc=glibc node=20.18.3
    loaded from: /nix/store/cyzz8f0yissb3gdkc8181h8db1lpil25-bitwarden-cli-2025.1.3/lib/node_modules/@bitwarden/clients/node_modules/argon2

Expected behaviour

Unlocking succeeds

Screenshots

No response

Relevant log output

Additional context

No response

System metadata

• system: "x86_64-linux"
• host os: Linux 6.13.7, NixOS, 25.05 (Warbler), 25.05.20250315.c80f6a7
• multi-user?: yes
• sandbox: yes
• version: nix-env (Nix) 2.24.12
• channels(root): "nixos"
• nixpkgs: /nix/store/alzxn3hjisc84hrlv44x6hni48crww26-source

Notify maintainers

@dotlambda

---

Note for maintainers: Please tag this issue in your pull request description. (i.e. Resolves #ISSUE.)

I assert that this issue is relevant for Nixpkgs

• I assert that this is a bug and not a support request.
• I assert that this is not a duplicate of an existing issue.
• I assert that I have read the NixOS Code of Conduct and agree to abide by it.

Is this issue important to you?

Add a 👍 reaction to issues you find important.

[dotlambda]

bisected to 0cebbcb (#378937)
Maybe the issue is --ignore-scripts?
cc @Tobix99 @wolfgangwalther @eclairevoyant

[TomaSajt]

What I do usually if npm fails without --ignore-scripts is that I run with --ignore-scripts then remove/patch out the failing script, then run npm rebuild to run the scripts that were skipped previously

Also note: #376765 added --ignore-scripts to vaultwarden too. Is that also broken perhaps?