Seeing captureException is not a function error

[azymnis]

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

7.110.0

Framework Version

18.2.0

Link to Sentry event

No response

SDK Setup

Sentry.init({
      dsn: SentryDSNURL,
      environment: isStaging() ? 'staging' : 'prod',
      maxValueLength: 1_000_000,
      integrations: [
        // enable HTTP calls tracing
        new Sentry.Integrations.Http({ tracing: true }),
        // enable Express.js middleware tracing
        new Sentry.Integrations.Express({ app }) as any,
        new ProfilingIntegration() as any,
      ],

      // Performance Monitoring
      tracesSampleRate: 1.0, // Capture 100% of the transactions, reduce in production!
      // Set sampling rate for profiling - this is relative to tracesSampleRate
      profilesSampleRate: 1.0, // Capture 100% of the transactions, reduce in production!
    });

Steps to Reproduce

This error does not happen always. In some cases we get this error message in the sentry express error handler:

this.getScope(...).captureException is not a function

This does not happen consistently and so is hard to reproduce

Expected Result

Not seeing this error

Actual Result

Error messages get swallowed by sentry

[mydea]

Hello,

can you make sure that all your SDK packages have the same version? When in doubt, you can remove your node_modules & lockfile and re-run npm install or yarn install. Often this kind of error comes from the package manager keeping some older versions of SDK dependencies (e.g. @sentry/core) around.

[azymnis]

@mydea we are using yarn and it seems from the lockfile that all versions are up to date at 7.110.0:

"@sentry/node@npm:^7.110.0":
  version: 7.110.0
  resolution: "@sentry/node@npm:7.110.0"
  dependencies:
    "@sentry-internal/tracing": "npm:7.110.0"
    "@sentry/core": "npm:7.110.0"
    "@sentry/types": "npm:7.110.0"
    "@sentry/utils": "npm:7.110.0"
  checksum: 10/400949e754cf8dbd819bd5c8f72d860c6f4b05d4af99741f12e7e4ce395d455297065b1658c021023cfe8a0adbcc6fb18d66e76c1ec7ebbe0021ca3e28ab6647
  languageName: node
  linkType: hard

The only issue I am seeing is that @sentry/profiling-node has a peer dependency on @sentry/node version ^7.44.1

"@sentry/profiling-node@npm:^1.3.5":
  version: 1.3.5
  resolution: "@sentry/profiling-node@npm:1.3.5"
  dependencies:
    detect-libc: "npm:^2.0.2"
    node-abi: "npm:^3.52.0"
    node-gyp: "npm:latest"
  peerDependencies:
    "@sentry/node": ^7.44.1
  bin:
    sentry-prune-profiler-binaries: scripts/prune-profiler-binaries.mjs
  checksum: 10/d83525fa19c73f7c28065e130e11942d6a43879651b4b8c8852bfb85efb10ead8a7803d7da337a7eab076f9f399f003520859026b04956b361d08ecf5ec9804b
  languageName: node
  linkType: hard

Could this be causing that?

[azymnis]

@mydea yup let me upgrade that one

[mydea]

As long as the actual version installed & being used is 7.110.0, it should be fine 🤔

So if you run:

yarn why @sentry/utils
yarn why @sentry/core

It should only give you 7.110.0, nothing else, basically.