Skip to content

[Bug]: @discordjs/opus@0.10.0 install fails on Node v24.11.1 (macOS arm64) #23733

@Sheetaa

Description

@Sheetaa

Description

Upgrade fails during npm install with @discordjs/opus@0.10.0 build error.

Environment

  • OpenClaw version: 2026.2.19-2
  • Node.js version: v24.11.1
  • npm version: 11.6.2
  • OS: macOS 26.2 (arm64)

Steps to reproduce

  1. Run openclaw update
  2. Error occurs during @discordjs/opus installation

Actual error

npm error code 1
npm error path /home/<user>/.../openclaw/node_modules/@discordjs/opus
npm error command failed
npm error command sh -c node-pre-gyp install --fallback-to-build

node-pre-gyp info using node-pre-gyp@0.4.5
node-pre-gyp info using node@24.11.1 | darwin | arm64
node-pre-gyp http GET https://github.com/discordjs/opus/releases/download/v0.10.0/opus-v0.10.0-node-v137-napi-v3-darwin-arm64-unknown-unknown.tar.gz
node-pre-gyp ERR! install response status 404 Not Found on https://github.com/discordjs/opus/releases/download/v0.10.0/opus-v0.10.0-node-v137-napi-v3-darwin-arm64-unknown-unknown.tar.gz
node-pre-gyp WARN Pre-built binaries not installable for @discordjs/opus@0.10.0 and node@24.11.1 (node-v137 ABI, unknown) (falling back to source compile with node-gyp)

gyp info using node-gyp@11.4.2
gyp info using node@24.11.1 | darwin | arm64

clang++: error: no such file or directory: 'Support/fnm/node-versions/v24.11.1/.../node-addon-api'
make: *** [Release/obj.target/opus/src/node-opus.o] Error 1
gyp ERR! build error
gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! System Darwin 25.2.0
gyp ERR! node -v v24.11.1
gyp ERR! node-gyp -v v11.4.2
gyp ERR! not ok

node-pre-gyp ERR! build error
node-pre-gyp ERR! node -v v24.11.1
node-pre-gyp ERR! node-pre-gyp -v v0.4.5
node-pre-gyp ERR! not ok

Root cause

  1. No pre-built binary for Node v24 (ABI v137): @discordjs/opus@0.10.0 does not ship a prebuilt binary for node-v137 (Node.js 24.x), causing a 404 when attempting to download it.
  2. Build path contains spaces: The fallback source compilation fails because the fnm installation path contains a space (Application Support), which causes clang++ to receive a truncated path for node-addon-api, resulting in a fatal compile error.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions