Usage of TextEncoderCommon causes compiler error in a setup without DOM Library

[smirowstanitzok]

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

Framework Version

No response

Link to Sentry event

No response

Steps to Reproduce

1. Setup a node project with typescript but without including DOM. For example tsconfig.json:

{
  "compilerOptions": {
  ...
  "lib": ["ES2020"],
  ...
  }
}

2. Install the newest version of @sentry/node: npm install @sentry/node.
3. Use tsc to compile the project.

Expected Result

The code can compile cleanly.

Actual Result

With #5004 comes the usage of TextEncoderCommon. This forces us to use the DOM library, which we can't and actually don't want to do.

Error: node_modules/@sentry/types/types/transport.d.ts(15,39): error TS2304: Cannot find name 'TextEncoderCommon'.

Maybe you can find an alternative without using the DOM library. Maybe more packages as a dependency can be a possible way. That would help us a lot to continue using sentry with pleasure. Thanks a lot.

[lforst]

Hi @smirowstanitzok, thanks for reporting this. Yup, I see the problem. We'll try to get it fixed soon.

For now, until we fix this, Instead of adding the dom library, you could try adding a global declaration looking like

// globals.d.ts

declare interface TextEncoderCommon {
  readonly encoding: string;
}