`@sentry/tracing` raises type errors in TS node.js project

[jtomaszewski]

We've just upgraded to @sentry/tracing 5.24.2 from @sentry/apm 5.21.1 and now get such error while trying to build our node.js project:

Our tsconfig.json:

{
 "compilerOptions": {
 "target": "es2017",
 "outDir": "build/main",
 "rootDir": "src",
 "moduleResolution": "node",
 "module": "commonjs",
 "declaration": true,
 "inlineSourceMap": true,
 "esModuleInterop": true /* Enables emit interoperability between CommonJS and ES Modules via creation of namespace objects for all imports. Implies 'allowSyntheticDefaultImports'. */,

 "strict": true,

 /* Additional Checks */
 "noUnusedLocals": true /* Report errors on unused locals. */,
 "noUnusedParameters": true /* Report errors on unused parameters. */,
 "noImplicitReturns": true /* Report error when not all code paths in function return a value. */,
 "noFallthroughCasesInSwitch": true /* Report errors for fallthrough cases in switch statement. */,

 /* Debugging Options */
 "traceResolution": false /* Report module resolution log messages. */,
 "listEmittedFiles": false /* Print names of generated files part of the compilation. */,
 "listFiles": false /* Print names of files part of the compilation. */,
 "pretty": true /* Stylize errors and messages using color and context. */,

 /* Experimental Options */
 // "experimentalDecorators": true /* Enables experimental support for ES7 decorators. */,
 // "emitDecoratorMetadata": true /* Enables experimental support for emitting type metadata for decorators. */,

 "lib": ["es2017"],
 "types": ["node", "jest"],
 "typeRoots": ["node_modules/@types", "src/types"]
 },
 "include": ["src/**/*.ts"],
 "exclude": ["node_modules/**"],
 "compileOnSave": false
}

On first look, it looks similar to the problem from #1530 . This is node.js project and we'd prefer not to require dom types in it.

[gabrielcardetti]

I just had the same problem but adding that library solved it. Why do you prefer not to add it?

[jtomaszewski]

@gabrielcardetti I guess, To not give the false impression in my project that browser specific stuff like global "Response" object exist, for example. Would drive the type checking a bit farther from reality.

[wbobeirne]

Looks like this was changed here: 0ee0799#diff-02c0b056ad9379483f05b887e87e58c62f44993fb997a0b70ca9f48e3a31642dL51-R55. It's just any now, this can be closed.

[jtomaszewski]

Yeah, should be good now I guess. Can't test it at the moment, but I think the issue can be closed. (Can be reopened if it still appears.)