Test failures on AIX

[mhdawson]

Since April 19 there seem to be test failures on AIX - https://ci.nodejs.org/view/x%20-%20Abi%20stable%20module%20API/job/node-test-node-addon-api-new/nodes=aix72-ppc64/10225/console

They seems to be at the npm install step:

npm-cache
npmrc
Cloning into 'node-addon-api'...
npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported
npm warn deprecated inflight@1.0.6: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
npm error code 1
npm error path /home/iojs/build/workspace/node-test-node-addon-api-new/nodes/aix72-ppc64/node-addon-api/node_modules/unrs-resolver
npm error command failed
npm error command bash -c napi-postinstall unrs-resolver check
npm error [napi-postinstall@0.1.6] Trying to install package "@unrs/resolver-binding-wasm32-wasi" using npm
npm error [napi-postinstall@0.1.6] Failed to install package "@unrs/resolver-binding-wasm32-wasi" using npm: Command failed: npm install --loglevel=error --prefer-offline --no-audit --progress=false --cpu=wasm32 @unrs/resolver-binding-wasm32-wasi@1.7.0
npm error npm error code EBADPLATFORM
npm error npm error notsup Unsupported platform for @unrs/resolver-binding-wasm32-wasi@1.7.0: wanted {"cpu":"wasm32"} (current: {"cpu":"ppc64"})
npm error npm error notsup Valid cpu:  wasm32
npm error npm error notsup Actual cpu: ppc64
npm error npm error A complete log of this run can be found in: /home/iojs/build/workspace/node-test-node-addon-api-new/nodes/aix72-ppc64/npm-cache/_logs/2025-04-24T15_54_43_834Z-debug-0.log
npm error
npm error [napi-postinstall@0.1.6] Trying to download "https://registry.npmjs.org/@unrs/resolver-binding-wasm32-wasi/-/resolver-binding-wasm32-wasi-1.7.0.tgz"
npm error [napi-postinstall@0.1.6] Failed to download "https://registry.npmjs.org/@unrs/resolver-binding-wasm32-wasi/-/resolver-binding-wasm32-wasi-1.7.0.tgz": Could not find "package/resolver.wasm32-wasi.node" in archive
npm error /home/iojs/build/workspace/node-test-node-addon-api-new/nodes/aix72-ppc64/node-addon-api/node_modules/napi-postinstall/lib/index.js:140
npm error                     throw new Error(`Failed to install package "${pkg}": ${(0, helpers_js_1.getErrorMessage)(err)}`);
npm error                           ^
npm error
npm error Error: Failed to install package "@unrs/resolver-binding-wasm32-wasi": Could not find "package/resolver.wasm32-wasi.node" in archive
npm error     at checkAndPreparePackage (/home/iojs/build/workspace/node-test-node-addon-api-new/nodes/aix72-ppc64/node-addon-api/node_modules/napi-postinstall/lib/index.js:140:27)
npm error     at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
npm error
npm error Node.js v22.15.0
npm error A complete log of this run can be found in: /home/iojs/build/workspace/node-test-node-addon-api-new/nodes/aix72-ppc64/npm-cache/_logs/2025-04-24T15_53_39_915Z-debug-0.log

[richardlau]

I'm not sure yet what path has led to installing unrs-resolver, but that module was updated on 19 April to include a new napi-postinstall dependency to "workaround npm's bug":

• [BUG] Platform-specific optional dependencies not being included in package-lock.json when reinstalling with node_modules present npm/cli#4828

https://github.com/un-ts/napi-postinstall is new (created on the same 19 April 2025) and it probably doesn't know what to do with AIX, e.g. https://github.com/un-ts/napi-postinstall/blob/b2917626cf9f315afed00384a25354a7958848f9/src/helpers.ts#L170-L249.

[mhdawson]

This seems to be the related npm tree that pulls it in:

─┬ neostandard@0.12.1
│ ├─┬ eslint-import-resolver-typescript@3.10.1
│ │ ├── @nolyfill/is-core-module@1.0.39
│ │ ├── debug@4.4.0 deduped
│ │ ├── eslint-plugin-import-x@4.10.6 deduped
│ │ ├── UNMET OPTIONAL DEPENDENCY eslint-plugin-import@*
│ │ ├── eslint@9.25.1 deduped
│ │ ├─┬ get-tsconfig@4.10.0
│ │ │ └── resolve-pkg-maps@1.0.0
│ │ ├─┬ is-bun-module@2.0.0
│ │ │ └── semver@7.7.1 deduped
│ │ ├── stable-hash@0.0.5
│ │ ├─┬ tinyglobby@0.2.13
│ │ │ ├─┬ fdir@6.4.4
│ │ │ │ └── picomatch@4.0.2 deduped
│ │ │ └── picomatch@4.0.2 deduped
│ │ └─┬ unrs-resolver@1.7.0
│ │   ├── UNMET OPTIONAL DEPENDENCY @unrs/resolver-binding-darwin-arm64@1.7.0
│ │   ├── UNMET OPTIONAL DEPENDENCY @unrs/resolver-binding-darwin-x64@1.7.0
│ │   ├── UNMET OPTIONAL DEPENDENCY @unrs/resolver-binding-freebsd-x64@1.7.0
│ │   ├── UNMET OPTIONAL DEPENDENCY @unrs/resolver-binding-linux-arm-gnueabihf@1.7.0
│ │   ├── UNMET OPTIONAL DEPENDENCY @unrs/resolver-binding-linux-arm-musleabihf@1.7.0
│ │   ├── UNMET OPTIONAL DEPENDENCY @unrs/resolver-binding-linux-arm64-gnu@1.7.0
│ │   ├── UNMET OPTIONAL DEPENDENCY @unrs/resolver-binding-linux-arm64-musl@1.7.0
│ │   ├── UNMET OPTIONAL DEPENDENCY @unrs/resolver-binding-linux-ppc64-gnu@1.7.0
│ │   ├── UNMET OPTIONAL DEPENDENCY @unrs/resolver-binding-linux-riscv64-gnu@1.7.0
│ │   ├── UNMET OPTIONAL DEPENDENCY @unrs/resolver-binding-linux-riscv64-musl@1.7.0
│ │   ├── UNMET OPTIONAL DEPENDENCY @unrs/resolver-binding-linux-s390x-gnu@1.7.0
│ │   ├── @unrs/resolver-binding-linux-x64-gnu@1.7.0
│ │   ├── @unrs/resolver-binding-linux-x64-musl@1.7.0
│ │   ├── UNMET OPTIONAL DEPENDENCY @unrs/resolver-binding-wasm32-wasi@1.7.0
│ │   ├── UNMET OPTIONAL DEPENDENCY @unrs/resolver-binding-win32-arm64-msvc@1.7.0
│ │   ├── UNMET OPTIONAL DEPENDENCY @unrs/resolver-binding-win32-ia32-msvc@1.7.0
│ │   ├── UNMET OPTIONAL DEPENDENCY @unrs/resolver-binding-win32-x64-msvc@1.7.0
│ │   └── napi-postinstall@0.1.6

[mhdawson]

neostandard has been pulled in for quite some time (at least 5 months or longer) and was last updated 4 months ago.

[mhdawson]

In eslint-import-resolver-typescript is says - "unrs-resolver": "^1.6.2" so it does make sense we'd be pulling in the changes @richardlau pointed to earlier and that would be causing the issue.

[mhdawson]

Checking to see if a short term work around might be to make sure we don't install dev dependencies in the CI job.

[mhdawson]

@abmusse could you take a look at PRing in the case needed for AIX into unrs-resolver?

[richardlau]

Checking to see if a short term work around might be to make sure we don't install dev dependencies in the CI job.

@mhdawson another short term work around might be using npm overrides to downgrade unrs-resolver.

[mhdawson]

Added the part which strips neostandard from the list of deps in an existing block for aix as follows:

  if [ $OS == "aix" ]; then
    # otherwise the default shell is used and we may get errors about "--" not being supported
    npm config set script-shell "bash"
    mv package.json package.json.org
    cat package.json.org |grep -v neostandard >package.json 
  fi

Tests passes. I think that is a reasonable work around until we can get unrs fixed up. @richardlau the overrides is a good suggestion as well, but I think I'll leave it at the fix in the job as that will avoid having to remove the override later on.

Will leave this issue open so we don't forget to follow up on the fix in unrs-resolver.

[mhdawson]

Passing test run - https://ci.nodejs.org/job/node-test-node-addon-api-new/10229/

[abmusse]

@abmusse could you take a look at PRing in the case needed for AIX into unrs-resolver?

@mhdawson
This is now on my TODO list and will be making the PR

[legendecas]

@abmusse would you mind confirming if this is resolved? thank you