Could not find a declaration file for module '@sentry/node'

[bonesoul]

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

6.19.0

Framework Version

No response

Link to Sentry event

No response

Steps to Reproduce

updated to 6.19.0 and now missing typescript definitions;

Error: src/lib/sentry.ts(7,25): error TS7016: Could not find a declaration file for module '@sentry/node'. '/home/runner/work/vizesizgezi.com/vizesizgezi.com/tasks/node_modules/@sentry/node/dist/index.js' implicitly has an 'any' type.

Expected Result

definitions.

Actual Result

none

[AbhiPrasad]

Hey thanks for reporting, we are taking a look!

[RobinCsl]

It seems related to #4724

[lforst]

@bonesoul we changed where we store the type definitions in the package. Could you provide information

• about your typescript setup (ie. tsconfig and/or any CLI options)?
• on how you're importing the SDK?

[nshyam97]

@lforst Same issues with @sentry/react. Using a tsconfig file and using Sentry.init within the ts file to initialise sentry

[Bobakanoosh]

@lforst On a fresh typescript package, after running pnpm i @sentry/node, and importing like import * as Sentry from "@sentry/node" the types are not recognized properly

[Lms24]

Hi everyone, we've identified the issue and we're working on a fix. This unfortunately affects most of the JS SDKs. We'll release a patch ASAP.

[lforst]

Hi everyone! We just published a patch for the package (6.19.1). Please let us know if updating to the newest version fixes the issue for you!

[n4bb12]

Hi everyone! We just published a patch for the package (6.19.1). Please let us know if updating to the newest version fixes the issue for you!

Yes, 6.19.1 fixed it for us. Thank you very much.

[lforst]

Yes, 6.19.1 fixed it for us. Thank you very much.

Great to hear! I will mark this issue as resolved.

Thanks @bonesoul for raising the issue and @RobinCsl for helping us find the cause!

[devguydavid]

Looks like it is working. Thanks!