[BUG] Client-side error (".jsx is not a function") in production (minified) NextJS app

[thomasmost]

Describe the bug

We are using NextJS. We have used react-tooltip v4 with no problem. We have wrapped it with the mounting effect to avoid SSR errors. When we update to v5, we get an application (client-side) error in production that reads a.jsx is not a function. The library functions fine in development.

Version of Package
v5.9.1

To Reproduce
deploy a production build of a NextJS app using a tooltip of this version—navigate to the page. Note that this is a run-time application error, not a build error.

Expected behavior
It should not crash the application

Screenshots

Desktop (please complete the following information if possible or delete this section):

• MacOS
• Firefox
• 110.0.1 (64-bit)
• React 18 / Next 13

Additional context
We are also using a turbo-repo, though I don't expect that's the issue

[nipunahh]

+1 for this. Our production is also gone now 😪

[gabrieljablonski]

Do you mind creating a sample project to help us debug the issue? Just a simple NextJS project with the tooltip.

For now, please try v5.8.3 and see if it still happens.
We switched from rollup to esbuild on v5.9.0, so that might be the cause.

[nipunahh]

@gabrieljablonski Same issue on v5.8.3 as well

[smurf-ss]

I fixed version "react-tooltip": "^5.8.3" to "react-tooltip": "5.8.3".
It worked in production. @gabrieljablonski @nipunahh

[danielbarion]

Hi guys, can someone create a sample project with this issue, please?

We will take a look as soon as possible when someone provides a sample project. Thanks!

[briva]

Same here downgrade to 5.8.3 fixed the pb

[devilsgeographer]

I have the same issue. If I set swcMinify: false in next.config.js, the error goes away.

Changing from "react-tooltip": "^5.7.4", to "react-tooltip": "5.8.3", also resolves it.

[thomasmost]

@gabrieljablonski and @danielbarion Sorry about the delay, here ya go: https://github.com/thomasmost/react-tooltip-repro

Reproduced with the latest version (5.10)

Steps to repro:

1. Clone the above repository
2. npx next build
3. npx next export
4. npx serve out
5. Navigate to localhost:3000

Thank you!

[gabrieljablonski]

@thomasmost Thanks for taking the time. As @devilsgeographer mentioned, you can set swcMinify: false on next.config.js as a workaround to this issue.

We'll be investigating why this is happening, but it seems to be an issue with the interaction between the default NextJS 13 minifier and our own bundling/minification process.

The issue will stay open until we figure it out.

[thomasmost]

@gabrieljablonski Glad to help! And no problem at all, as others have also mentioned, 5.8.3 doesn't seem to have this behavior. So I think I'm set for the time being 🙂

[nipunahh]

Thanks a lot @thomasmost - you're a lifesaver