Sentry node profiler crashen on non-LTS nodejs version

[drago1520]

Environment

self-hosted (https://develop.sentry.dev/self-hosted/)

Steps to Reproduce

1. Install Node 25 or any other non-LTS version
2. try to run Node sampling. I'm using Astro

When you start the server, it'll crash.

Expected Result

The server should start

Actual Result

Crashes with

12:52:10 [ERROR] Error: Cannot find module './sentry_cpu_profiler-win32-x64-141.node'       
Require stack:
- C:\projects\research\astro\node_modules\@sentry\node-cpu-profiler\lib\index.js
    at Module._resolveFilename (node:internal/modules/cjs/loader:1475:15)
    at wrapResolveFilename (node:internal/modules/cjs/loader:1048:27)
    at defaultResolveImplForCJSLoading (node:internal/modules/cjs/loader:1072:10)
    at resolveForCJSWithHooks (node:internal/modules/cjs/loader:1093:12)
    at Module._load (node:internal/modules/cjs/loader:1261:25)
    at wrapModuleLoad (node:internal/modules/cjs/loader:255:19)
    at Module.require (node:internal/modules/cjs/loader:1575:12)
    at require (node:internal/modules/helpers:191:16)
    at importCppBindingsModule (C:\projects\research\astro\node_modules\@sentry\node-cpu-profiler\lib\index.js:186:12)
    at Object.<anonymous> (C:\projects\research\astro\node_modules\@sentry\node-cpu-profiler\lib\index.js:188:38)

It cannot find 141 (Node 24 LTS), because I had Node 25.

I understand you cannot ship bindings for all node versions, but the error message could be improved.

Product Area

Issues

Link

No response

DSN

No response

Version

No response

[linear-code]

ENG-8332

[getsantry]

Auto-routing to @getsentry/product-owners-issues for triage ⏲️

[Mahnoor-Zaffar]

Hey looks like the profiler crashes on non-LTS Node versions, I'll add support for that