unable to compile "Cannot find name 'Element'"

[FrederikPriede]

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 package are you using?

@sentry/node

SDK Version

7.12.0

Framework Version

No response

Link to Sentry event

No response

Steps to Reproduce

• create empty folder
• switch to newly created folder
• npm init (use defaults)
• npm i @sentry/node @types/node typescript
• npx tsc --init (create vanilla tsconfig)
• change lib property within tsconfig.json to ES2020
• change skipLibCheck to false
• create simple source file test.ts

import { captureException } from "@sentry/node";
captureException(new Error());

• run npx tsc

Expected Result

test.ts should compile to test.js

Actual Result

Compiling fails with this error:

node_modules/@sentry/utils/types/browser.d.ts:22:58 - error TS2304: Cannot find name 'Element'.
22 export declare function getDomElement(selector: string): Element | null;
                                                            ~~~~~~~
Found 1 error in node_modules/@sentry/utils/types/browser.d.ts:22

[FrederikPriede]

I found some workarounds for this:

• revert the version of @sentry/node back to 7.11.1
• add DOM to the lib option within your tsconfig (or use the --libparam of tsc)
• set skipLibCheck option to false or remove it completly

Sadly, I cant use any of those workarounds. I think this issue was introduced with #5594. Interestingly a very similar issue happened earlier this year, see #4449. @AbhiPrasad fixed this issue with #4451, removing all references to DOM.

[Lms24]

Hi @FrederikPriede thanks for reporting. I agree, this is caused by #5594. We'll fix this and include it in the next release.

[AbhiPrasad]

Let's actually get this out ASAP to unblock TS users - I'll open a patch.

[Lms24]

Hi @FrederikPriede we just released a patch (7.12.1) with the fix