@sentry/profiling-node bindings for Node 21

[rhinodavid]

Team,

I'm wondering if there is a policy against prebuilding bindings for non-LTS versions, specifically Node 21, which is current:

It looks like the workflow to compile bindings only has LTS versions (16/18/20).

As an aside: I thought that if there wasn't a prebuilt binding available then bindings would be built on install, but that doesn't seem to be happening for me with pnpm/darwin/x64: Cannot find module '<repo>/node_modules/.pnpm/@[email protected]/node_modules/@sentry/profiling-node/lib/sentry_cpu_profiler-darwin-x64-120.node' from '../../node_modules/.pnpm/@[email protected]/node_modules/@sentry/profiling-node/lib/index.js'

[rhinodavid]

Ahh I have some logs:

.../node_modules/@sentry/profiling-node install$ node scripts/check-build.js
.../node_modules/@sentry/profiling-node install: @sentry/profiling-node: No precompiled binary found
.../node_modules/@sentry/profiling-node install: @sentry/profiling-node: Compiling from source...
.../node_modules/@sentry/profiling-node install: > @sentry/[email protected] build:bindings:configure
.../node_modules/@sentry/profiling-node install: > node-gyp configure
.../node_modules/@sentry/profiling-node install: > @sentry/[email protected] build:bindings
.../node_modules/@sentry/profiling-node install: > node-gyp build && node scripts/copy-target.js
.../node_modules/@sentry/profiling-node install:   CXX(target) Release/obj.target/sentry_cpu_profiler/bindings/cpu_profiler.o
.../node_modules/@sentry/profiling-node install: @sentry/profiling-node: Failed to build bindings
.../node_modules/@sentry/profiling-node install: @sentry/profiling-node: gyp info it worked if it ends with ok
.../node_modules/@sentry/profiling-node install: gyp info using [email protected]
.../node_modules/@sentry/profiling-node install: gyp info using [email protected] | darwin | x64
.../node_modules/@sentry/profiling-node install: gyp info spawn make
.../node_modules/@sentry/profiling-node install: gyp info spawn args [ 'BUILDTYPE=Release', '-C', 'build' ]
.../node_modules/@sentry/profiling-node install: c++: error: unrecognized command line option '-stdlib=libc++'
.../node_modules/@sentry/profiling-node install: make: *** [Release/obj.target/sentry_cpu_profiler/bindings/cpu_profiler.o] Error 1
.../node_modules/@sentry/profiling-node install: gyp ERR! build error 
.../node_modules/@sentry/profiling-node install: gyp ERR! stack Error: `make` failed with exit code: 2
.../node_modules/@sentry/profiling-node install: gyp ERR! stack at ChildProcess.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:209:23)
.../node_modules/@sentry/profiling-node install: gyp ERR! System Darwin 23.2.0
.../node_modules/@sentry/profiling-node install: gyp ERR! command "/usr/local/bin/node" "/usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "build"
.../node_modules/@sentry/profiling-node install: gyp ERR! cwd /Users/davidwalsh/code-local/0x-labs/node_modules/.pnpm/@[email protected]/node_modules/@sentry/profiling-node
.../node_modules/@sentry/profiling-node install: gyp ERR! node -v v21.6.1
.../node_modules/@sentry/profiling-node install: gyp ERR! node-gyp -v v10.0.1
.../node_modules/@sentry/profiling-node install: gyp ERR! not ok
.../node_modules/@sentry/profiling-node install: Done

[AbhiPrasad]

I'm wondering if there is a policy against prebuilding bindings for non-LTS versions, specifically Node 21, which is current:

Generally yes, because profiling node relies on v8 bindings which are a lot more unstable on non-LTS versions. I don't think we'll change this for the time being.