Sentry.captureException is not a function

[maxpain]

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?

Self-hosted/on-premise

Which SDK are you using? If you use the CDN bundles, please specify the exact bundle (e.g. bundle.tracing.min.js) in your SDK setup.

@sentry/serverless

SDK Version

7.43.0

Framework Version

No response

Link to Sentry event

No response

SDK Setup

import * as Sentry from '@sentry/serverless'

Sentry.GCPFunction.init({
	dsn: '',
	environment: process.env.NODE_ENV,
})

Steps to Reproduce

Sentry.captureException(new Error('test'))

Expected Result

Don't crash

Actual Result

Crash

TypeError: Sentry.captureException is not a function
    at file:///Users/maxpain/dev/gptaskbot/src/index.ts:64:8
    at processTicksAndRejections (node:internal/process/task_queues:95:5)

[AbhiPrasad]

Hey @maxpain thanks for writing in!

As per https://unpkg.com/@sentry/serverless@7.42.0/cjs/index.js we should be exporting Sentry.captureException.

Did this start happening with the latest version? Are you using some bundling process when deploying to your serverless function?

[maxpain]

Hey @maxpain thanks for writing in!

As per https://unpkg.com/@sentry/serverless@7.42.0/cjs/index.js we should be exporting Sentry.captureException.

Did this start happening with the latest version? Are you using some bundling process when deploying to your serverless function?

Hello. I don't know, I just switched from @sentry/node to @sentry/serverless in my Google Cloud Function

[AbhiPrasad]

What happens if you import via a require call? I'm unable to reproduce this unfortunately.

Our serverless SDK just re-exports the Node SDK:

sentry-javascript/packages/serverless/src/index.ts

Line 7 in ba99e7c

export * from '@sentry/node';

What happens if you explicitly import captureException and use it?

const { captureException } = require('@sentry/serverless');

Are you able to provide a reproduction of some kind to help us debug further?

[maxpain]

@AbhiPrasad

const { captureException } = require('@sentry/serverless')
captureException(new Error('test'))

maxpain@Maksims-MacBook-Pro-2 webhooks % npx env-cmd ts-node --esm ./src/handle-gamemoney.ts
ReferenceError: require is not defined in ES module scope, you can use import instead
    at file:///Users/maxpain/dev/gptask/webhooks/src/handle-gamemoney.ts:1:30
    at ModuleJob.run (node:internal/modules/esm/module_job:193:25)

[AbhiPrasad]

maxpain@Maksims-MacBook-Pro-2 webhooks % npx env-cmd ts-node --esm ./src/handle-gamemoney.ts
ReferenceError: require is not defined in ES module scope, you can use import instead
    at file:///Users/maxpain/dev/gptask/webhooks/src/handle-gamemoney.ts:1:30
    at ModuleJob.run (node:internal/modules/esm/module_job:193:25)

This error makes sense, since you were calling ts-node with the --esm flag, which means that require does not work.

I tried reproducing this here: https://github.com/AbhiPrasad/GH-7441-captureException-not-a-function, but works fine for me. Are you sure you've installed your packages correctly?

[maxpain]

@AbhiPrasad Adding "type": "module" to package.json, which makes this package an ESM module, causes the error.

[AbhiPrasad]

Ah yeah I forgot to remove the require call:

diff --git a/src/handle-gamemoney.ts b/src/handle-gamemoney.ts
index 4545802..b6db55e 100644
--- a/src/handle-gamemoney.ts
+++ b/src/handle-gamemoney.ts
@@ -1,2 +1,2 @@
-const { captureException } = require("@sentry/serverless");
+import { captureException } from "@sentry/serverless";
 captureException(new Error("test"));

Now we should be using esm across the board! Running npx env-cmd ts-node --esm ./src/handle-gamemoney.ts seems to be fine! I don't get TypeError: Sentry.captureException is not a function.

[maxpain]

@AbhiPrasad
Here is repo for reproduction:
https://github.com/maxpain/GH-7441-captureException-not-a-function

[AbhiPrasad]

Thanks, was able to reproduce! I don't quite understand why this is happening though because we ship esm:

sentry-javascript/packages/serverless/package.json

Line 13 in d6561b8

"module": "build/npm/esm/index.js",

For some reason, ts-node is falling back to using commonjs.

The work around is like so

src/index.ts

import Sentry from "@sentry/serverless";
Sentry.captureException(new Error("test"));

[maxpain]

For some reason, ts-node is falling back to using commonjs.

No, the problem is not in ts-node.

maxpain@Maksims-MacBook-Pro-2 GH-7441-captureException-not-a-function % npx tsc
maxpain@Maksims-MacBook-Pro-2 GH-7441-captureException-not-a-function % node .build/index.js
file:///Users/maxpain/dev/GH-7441-captureException-not-a-function/.build/index.js:2
Sentry.captureException(new Error("test"));
       ^

TypeError: Sentry.captureException is not a function
    at file:///Users/maxpain/dev/GH-7441-captureException-not-a-function/.build/index.js:2:8
    at ModuleJob.run (node:internal/modules/esm/module_job:193:25)

Node.js v19.7.0