Deno 2.8.0 compatibility

[Webcretaire]

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/deno

SDK Version

10.53.1

Framework Version

2.8.0

Link to Sentry event

No response

Reproduction Example/SDK Setup

Hello, thanks for this great library

Deno recently released version 2.8.0, which breaks the Sentry SDK if I'm not mistaken : simply initializing Sentry gives an error and crashes the script

The exact same code was working well with Deno 2.7.14

Steps to Reproduce

1. Put the following content in a TS file :

import * as Sentry from "@sentry/deno";

Sentry.init({
 dsn: "<< myDsn >>",
 release: "myRelease",
 environment: "myEnvironment",
 sendDefaultPii: true,
 debug: true,
 skipOpenTelemetrySetup: true
});

2. Run with deno run -A myscript.ts (on latest Deno 2.8.0)

Expected Result

No error, Sentry initializes

Actual Result

The following error in terminal :

Sentry Logger [log]: Integration installed: InboundFilters
Sentry Logger [log]: Integration installed: RequestData
Sentry Logger [log]: Integration installed: FunctionToString
Sentry Logger [log]: Integration installed: LinkedErrors
Sentry Logger [log]: Integration installed: Dedupe
Sentry Logger [log]: Integration installed: Breadcrumbs
Sentry Logger [log]: Integration installed: DenoContext
error: Uncaught (in promise) TypeError: Cannot set property serve of #<Object> which has only a getter
 at Object.setupOnce (file:///my_source_folder/node_modules/.deno/@sentry+deno@10.53.1/node_modules/@sentry/deno/build/esm/integrations/deno-serve.js:52:12)
 at setupIntegration (file:///my_source_folder/node_modules/.deno/@sentry+core@10.53.1/node_modules/@sentry/core/build/esm/integration.js:118:104)
 at file:///my_source_folder/node_modules/.deno/@sentry+core@10.53.1/node_modules/@sentry/core/build/esm/integration.js:89:7
 at Array.forEach (<anonymous>)
 at setupIntegrations (file:///my_source_folder/node_modules/.deno/@sentry+core@10.53.1/node_modules/@sentry/core/build/esm/integration.js:86:16)
 at DenoClient._setupIntegrations (file:///my_source_folder/node_modules/.deno/@sentry+core@10.53.1/node_modules/@sentry/core/build/esm/client.js:1215:20)
 at DenoClient.init (file:///my_source_folder/node_modules/.deno/@sentry+core@10.53.1/node_modules/@sentry/core/build/esm/client.js:490:12)
 at initAndBind (file:///my_source_folder/node_modules/.deno/@sentry+core@10.53.1/node_modules/@sentry/core/build/esm/sdk.js:37:10)
 at Module.init (file:///my_source_folder/node_modules/.deno/@sentry+deno@10.53.1/node_modules/@sentry/deno/build/esm/sdk.js:111:18)
 at file:///my_source_folder/src/test.ts:3:8

Additional Context

No response

Priority

_{React with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding +1 or me too, to help us triage it.}

[linear-code]

JS-2603

[logaretm]

Thanks for reporting this, I have a fix in PR right now

[github-actions]

A PR closing this issue has just been released 🚀

This issue was referenced by PR #21155, which was included in the 10.54.0 release.