Can't see local variables on the sentry dashboard

[zstiggz]

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.26.0

Framework Version

No response

Link to Sentry event

https://visualelectric.sentry.io/share/issue/280ad0165d0b4e7f985ac7c5b26e7069/

Reproduction Example/SDK Setup

I can't see local variables logged in the sentry dashboard for my project.

Minimal example:

// test.js
import dotenv from 'dotenv'

if (process.env.NODE_ENV !== 'production') {
  dotenv.config({ path: '../.env' })
}
import * as Sentry from '@sentry/node'

Sentry.init({
  release: process.env.VE_SENTRY_RELEASE,
  dsn: process.env.VE_SERVER_SENTRY_DSN,
  environment: process.env.VE_ENVIRONMENT,
  includeLocalVariables: true,
})

function run() {
  console.log('test local vars...')
  const someVariable1 = undefined
  const someVariable2 = 2
  console.log(someVariable1.test)
}

run()

Steps to Reproduce

node test.js on the above example

Expected Result

I expect to be able to see the values of someVariable1 and someVariable2 in the sentry dashboard for the issue.

Actual Result

[AbhiPrasad]

Hey @CaptainStiggz.

As per https://docs.sentry.io/platforms/javascript/guides/node/configuration/options/#include-local-variables

Due to an open Node.js issue, we are currently unable to capture local variables for unhandled errors when using JavaScript modules (ESM).

To get around this, you'll need to explicity call Sentry.captureException in a try - catch if you are using ESM.

If you use one of our framework error handlers (setupExpressErrorHandler, setupFastifyErrorHandler) we call captureException in the request middleware, so local variables will be attached in esm.

[AbhiPrasad]

We need to improve our docs here.

[johnbulmansonos]

For anyone else who also might be experiencing this issue with a TS node project, I found the issue for me was happening when I was running my project locally with ts-node. I would see local variables reported to Sentry when I ran my javascript build directly from my dist output (I was using tsc && node dist/app.js). Not sure why this caused the issue, but I also noticed that my debugger stopped working locally when Sentry is enabled locally, so it could be possible that ts-node and Sentry are trying to race for some sort of Node Inspector lock.

[chargome]

@jpbulman-sonos your ts-node config might also emit ESM, could be the case that you run into same issue because of that