Can't resolve 'react/jsx-runtime' in xxx/node_modules/@sentry/react/esm

[htCaoHaitao]

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

SDK Version

8.5.0

Framework Version

React: 17.0.2

Link to Sentry event

No response

SDK Setup

No response

Steps to Reproduce

1、update sentry sdk version

yarn upgrade @sentry/[email protected] @sentry/[email protected]

2、run project in local

yarn start

Expected Result

The project run with no error as shown below ：

Actual Result

[lforst]

Hi, would you mind sharing a small reproduction example we could clone to check this error out? It is usually quite hard to troubleshoot build errors without having access to the bigger picture because there is usually so much configuration involved. Thanks!

[webdevian]

Getting same error on @sentry/[email protected] and on @sentry/[email protected] when I tried last week. With [email protected]. Node v20.6.1

Module not found: Error: Can't resolve 'react/jsx-runtime' in 'node_modules/@sentry/react/esm'
Did you mean 'jsx-runtime.js'?
BREAKING CHANGE: The request 'react/jsx-runtime' failed to resolve only because it was resolved as fully specified
(probably because the origin is strict EcmaScript Module, e. g. a module with javascript mimetype, a '*.mjs' file, or a '*.js' file where the package.json contains '"type": "module"').
The extension in the request is mandatory for it to be fully specified.
Add the extension to the request.

The error seems to be referring to
import { jsx } from 'react/jsx-runtime'; in node_modules/@sentry/react/esm/errorboundary.js
and
{"type":"module","sideEffects":false} in node_modules/@sentry/react/esm/package.json

[baw]

We have been having this issue in @sentry/react in every version since version 8.5.0

[lforst]

Hi @webdevian and @baw! It would be amazing if you could share a small reproduction example where this is happening.

[pieterbeulque]

+1 for @baw, it's hard to set up a minimal reproduction though. It looks like it might be related with us using React 17 and React Router 6, but I'm not 100% sure.

[baw]

We've seen this in one app when it was running React 16 and it continues after it was upgraded to React 17. I don't think it's a React issue.

I only see this in one of our apps and we have other apps running the latest version of @sentry/react without any issues.

I'd rather spend the time fixing the issue in our app and then get back to you than make a small reproduction example.

[AbhiPrasad]

Due to the variety of permutations of how you can set up a react app, we really need a reproduction to dive into this. Even just sharing your bundler config and showing how you are importing Sentry would be a great help!

[marcospachecows]

I've been seeing the same error after I upgraded @sentry/react from ^7.114.0 to ^8.12.0 using the npx @sentry/migr8@latest command. My React version is ^16.6.0:

{
    "dependencies": {
        ...
        "react": "^16.6.0",
        "react-dom": "^16.6.0",
        "react-router": "^5.2.1",
        "react-router-dom": "^5.3.0",
        "@sentry/react": "^8.12.0"
        ...
    }
}

[AbhiPrasad]

Our peer deps state we only support 16.14.0 or higher:

sentry-javascript/packages/react/package.json

Line 52 in aafb4e7

"react": "^16.14.0 || 17.x || 18.x || 19.x"

Could you upgrade your react version to 16.14.0 and check if the error still exists?

[marcosdiasdev]

I've got the same error message while trying to build an application with "react": "^17.0.2" and "@sentry/react": "^8.13.0". Downgrading Sentry to "@sentry/react": "^7.118.0" fixed it.

[lforst]

@marcosdiasdev I would like to reiterate, this issue needs reproduction. To look into this further, we need a way to reproduce this error. Please provide a stackblitz or github repo, or something similar. Thanks!

[pieterbeulque]

@lforst here you go: https://github.com/pieterbeulque/getsentry-sentry-javascript-12608/commits/main/

Run npm run build and you'll see that 8.4.0 works, 8.5.0 onwards fails.

Given the error I assume it's a combination of Webpack + Babel + React 17 + whatever changes you made going from 8.4 to 8.5. (I left some other React-adjacent packages in the dependencies but I think they may be irrelevant. Edit: removed)

[lforst]

@pieterbeulque awesome thanks! I'll take a look.

[pieterbeulque]

That was fast, thanks @lforst.

[nocive]

Still running into the same issue with 8.14 (vitest).

Looking at the source code, it doesn't look like the fix had any actual effect on the resulting code since I still see the incorrect import being used.

[alexandersorokin]

I have encountered such an issue several times with other packages.

Upgrading to react@18 should fix the issue. Also configuring a bundler alias can fix the issue. Also not using esm can fix the issue.

But I have found no way to fix the issue on package side (like @sentry/react) for both react@17 and react@18.
react@17 doesn't have an exports field in package.json and requires react/jsx-runtime.js (with extension).
react@18 does have the exports field in package.json and support react/jsx-runtime only without extension.

[pieterbeulque]

@lforst - As mentioned above, looks like the fix doesn't actually fix it. Updated the reproduction repo.

[lforst]

Update: We're gonna move back to the classic runtime because we discovered issues with a non-faulty fix. The "fix" we merged actually did nothing because I made a mistake while testing. This will cause warnings in React 19, maybe we can find a way to provide a separate package or submodule exports for the new runtime when React 19 ships stably.

[nocive]

thanks for the fast fix & release guys, works now 🎉