Beta version: Cannot read properties of undefined (reading 'current')

[binomialstew]

Describe the bug
I'm seeing Cannot read properties of undefined (reading 'current') in beta version 5.10.1-beta-9. I do not see this error in 5.10.1-beta.4.

Looks like ReactCurrentOwner.current is undefined.

[danielbarion]

hi @binomialstew can you check our PRs and the comments (beta releases) and let me know if the latest beta releases work for you?

#984 yarn add [email protected] - rollup

#982 yarn add [email protected] - esbuild

[binomialstew]

Hi @danielbarion , I do not see the error in [email protected]. Unfortunately, that still contains the minification issue that I was looking at yesterday. beta-9 is the version where I saw the issue I raised here. So far, 5.10.1-beta.4 is functionally working but causes an eslint warning that we need to work around.

[gabrieljablonski]

Same as said on #987.

Please test out [email protected] and let us know about this specific issue.

[binomialstew]

I don't see this issue any longer, but I do see this when trying to access the tooltip in a [email protected] production build:

floating-ui.core.browser.min.mjs:1 Uncaught (in promise) TypeError: f is not a function
    at d (floating-ui.core.browser.min.mjs:1:860)

[gabrieljablonski]

Can you try [email protected]? Apparently this version fixed a similar issue for us, so I'd appreciate if you could test it.

[binomialstew]

This does appear to be fixed by using that version of next.js. For some reason, noArrow is not applying the class necessary to hide the arrow in your 5.10.2-beta.x. It's undefined on the div.react-tooltip-arrow element. This was working correctly in 5.10.1-beta.4.

I was unable to find branches that correspond to these beta releases. Are they here? I'd be able to provide more helpful info to you and make some things more clear to myself if I could take a look at the diffs.

[gabrieljablonski]

For some reason, noArrow is not applying the class necessary to hide the arrow in your 5.10.2-beta.x

Just a slight oversight when refactoring some class names. Already fixed, thanks for reporting.

Regarding this issue we are considering it as a bug on Next.js, since the update fixes it.

[email protected] has been released, and it addresses the other issues that were closed today.