Regression: Error [ERR_INSPECTOR_NOT_AVAILABLE]: Inspector is not available when using vercel/pkg

[munelear]

Is there an existing issue for this?

• I have checked for existing issues https://github.com/getsentry/sentry-javascript/issues
• I have reviewed the documentation https://docs.sentry.io/
• I am using the latest SDK release https://github.com/getsentry/sentry-javascript/releases

How do you use Sentry?

Sentry Saas (sentry.io)

Which SDK are you using?

@sentry/node

SDK Version

8.4.0

Framework Version

No response

Link to Sentry event

No response

SDK Setup

No response

Steps to Reproduce

1. Build app with Sentry SDK 8.4.0 using pkg
2. Run app and experience crash

I verified that using sentry 7.31.0 does not have this issue, as noted in issue #6769, this was previously fixed and at some point regressed.

Expected Result

App should not crash

Actual Result

Error [ERR_INSPECTOR_NOT_AVAILABLE]: Inspector is not available
    at new NodeError (node:internal/errors:388:5)
    at node:inspector:23:9
    at NativeModule.compileForInternalLoader (node:internal/bootstrap/loaders:329:7)
    at NativeModule.compileForPublicLoader (node:internal/bootstrap/loaders:269:10)
    at loadNativeModule (node:internal/modules/cjs/helpers:49:9)
    at Module._load (node:internal/modules/cjs/loader:792:20)
    at Module.require (node:internal/modules/cjs/loader:1012:19)
    at Module.require (pkg/prelude/bootstrap.js:1851:31)
    at require (node:internal/modules/cjs/helpers:102:18)
    at 86592 (/snapshot/dist/main.js) {
  code: 'ERR_INSPECTOR_NOT_AVAILABLE'
}

[munelear]

The regression appears to have happened in the 8.0.0 release timeframe. I am unable to reproduce this issue on 7.116.0.

[mydea]

Hey, thanks for writing in. What version of node are you using/running this in?

[AbhiPrasad]

Fix released with https://github.com/getsentry/sentry-javascript/releases/tag/8.5.0

[munelear]

FYI- I tried pulling in release 8.5.0 but I was still experiencing this issue. I'll re-review the release documentation and check if there's something wrong on my end, but I wanted to give you a heads up that this may not be completely resolved yet.