Repository navigation
Sentry node profiler crashen on non-LTS nodejs version #22970
Description
Environment
self-hosted (https://develop.sentry.dev/self-hosted/)
Steps to Reproduce
- Install Node 25 or any other non-LTS version
- 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
Metadata
Metadata
Assignees
Projects
- Status
Activity
linear-code commentedon Jul 31, 2026
ENG-8332
JS-3250
getsantry commentedon Jul 31, 2026
Auto-routing to @getsentry/product-owners-issues for triage ⏲️
Mahnoor-Zaffar commentedon Jul 31, 2026
Hey looks like the profiler crashes on non-LTS Node versions, I'll add support for that
Lms24 commentedon Aug 4, 2026
Thanks for reporting! I don't think we'll add binaries for non-LTS versions but you're right, the error for the fallback import happening here:
https://github.com/getsentry/sentry-javascript-profiling-node-binaries/blob/9ff52e0802a29ea70bffdf551f533f9de3cae558/src/index.ts#L185
should be improved. I'll open a PR for that.
That being said, you should already see this console log:
Lms24 commentedon Aug 4, 2026
Opened getsentry/sentry-javascript-profiling-node-binaries#39
Lms24 commentedon Aug 4, 2026
@drago1520 I released a new version of
@sentry/node-cpu-profiler. If you bump to2.4.3you should get a better log message now. Also opened #22983 to make the bump automatically when the next SDK version is released.feat(deps): Bump `@sentry/node-cpu-profiler` to 2.4.3 (#22983)