pnpm install fails with Rust N-API panic due to napi-sys@2.3.0 on unsupported OS `msys2`

[Kreijstal]

thread '' panicked at C:\Users\runneradmin.cargo\registry\src\index.crates.io-6f17d22bba15001f\napi-sys-2.3.0\src\functions.rs:7:3:
Must load N-API bindings
note: run with RUST_BACKTRACE=1 environment variable to display a backtrace

when running pnpm install

[JounQin]

Reproduction please...

[Kreijstal]

Reproduction please...

ah yes I forgot, please follow the following steps.

first use windows, then install https://www.msys2.org/ or download https://github.com/msys2/msys2-installer/releases/download/2025-02-21/msys2-base-x86_64-20250221.tar.xz and then use msys_shell.cmd -here -defterm -no-start -ucrt64
in the shell update once using pacman -Syu
you can use pacboy for convenience
pacman -S pactoys
then install nodejs
pacboy -S nodejs:p

having this nodejs installed, use npm to install pnpm

npm install -g pnpm

then after this try

pnpm install unrs-resolver

If you are on linux or mac, you might try https://github.com/msys2/msys2-docker

[JounQin]

I don't have Window devices, so what're the reproduction steps for https://github.com/msys2/msys2-docker.

[Kreijstal]

Right now I can not test this (am on a bus so downloading docker out of internet data is not a good idea) but it is the same process as windows

docker run -it ghcr.io/msys2/msys2-docker-experimental <- after this you will should enter the msys2 shell then do
pacman -S pactoys --noconfirm && pacboy -S nodejs:p --noconfirm

npm install -g pnpm
pnpm install unrs-resolver

[Kreijstal]

btw nevermind about using wine/docker.

# node -p 'require("path").dirname(process.execPath)'

  #   [1380]: std::shared_ptr<node::InitializationResultImpl> node::InitializeOncePerProcessInternal(const std::vector<std::__cxx11::basic_string<char> >&, ProcessInitiali
  #   [1380]: std::shared_ptr<node::InitializationResultImpl> node::InitializeOncePerProcessInternal(const std::vector<std::__cxx11::basic_string<char> >&, ProcessInitialization
[0KF
lags::Flags) at src/node.cc:1144
  #  Assertion failed: ncrypto::CSPRNG(nullptr, 0)

----- Native stack trace -----

 1: 00006ffffa2e9c95
 2: 00006ffffa397562
 3: 00006ffffa34d4e9
 4: 00006ffffa34ebb5
 5: 0000000140001556
 6: 00000001400012ea
 7: 00000001400013f6
 8: 00006fffffee8d19
 9: 00006ffffff951fb

wine still is a WIP, so this needs a lil bit of work. it was still an experimental version, so sorry for the bad guidance, no it seems you still need a windows vm for now

[JounQin]

msys2 is not supported by nap-rs and not even Node.js itself officially... Can you try to install @unrs/resolver-binding-wasm32-wasi manually?

[JounQin]

@Kreijstal Can you helps to try install @unrs/resolver-binding-wasm32-wasi manually and enable environment NAPI_RS_FORCE_WASI=1?

[Kreijstal]

@Kreijstal Can you helps to try install @unrs/resolver-binding-wasm32-wasi manually and enable environment NAPI_RS_FORCE_WASI=1?

I can try that, wait

[Kreijstal]

@JounQin

user@win UCRT64 ~/git/unrs-resolver
$ npm i @unrs/resolver-binding-wasm32-wasi
npm error code EBADPLATFORM
npm error notsup Unsupported platform for @unrs/resolver-binding-wasm32-wasi@1.9.0: wanted {"cpu":"wasm32"} (current: {"cpu":"x64"})
npm error notsup Valid cpu:  wasm32
npm error notsup Actual cpu: x64
npm notice
npm notice New major version of npm available! 10.9.2 -> 11.4.2
npm notice Changelog: https://github.com/npm/cli/releases/tag/v11.4.2
npm notice To update run: npm install -g npm@11.4.2
npm notice
npm error A complete log of this run can be found in: C:\Users\user\AppData\Local\npm-cache\_logs\2025-06-13T08_45_02_108Z-debug-0.log

user@win UCRT64 ~/git/unrs-resolver
$ NAPI_RS_FORCE_WASI=1 npm i @unrs/resolver-binding-wasm32-wasi
npm error code EBADPLATFORM
npm error notsup Unsupported platform for @unrs/resolver-binding-wasm32-wasi@1.9.0: wanted {"cpu":"wasm32"} (current: {"cpu":"x64"})
npm error notsup Valid cpu:  wasm32
npm error notsup Actual cpu: x64
npm error A complete log of this run can be found in: C:\Users\user\AppData\Local\npm-cache\_logs\2025-06-13T08_47_32_588Z-debug-0.log

[JounQin]

@Kreijstal You need to install it with --cpu=wasm32 --force like https://github.com/un-ts/napi-postinstall/blob/9ce6cde865d33812ce135dbd1e522272f1fb6dc9/src/index.ts#L132

[Kreijstal]

@JounQin yay

added 131 packages, and audited 132 packages in 46s

27 packages are looking for funding
  run `npm fund` for details

found 0 vulnerabilities

[JounQin]

So does using NAPI_RS_FORCE_WASI=1 work for you now?

[Kreijstal]

it does install, now I need to test if it works.. but for now it seems to just install, yes