-
Notifications
You must be signed in to change notification settings - Fork 93
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Plugins error (even though not loading any plugins) #379
Comments
Same issue. Not using the new app directory, so not sure what the fallout is from this last upgrade... Been meaning to drop this dead package for awhile now... guess that time has come. |
Likely a Next.js minification bug, was also filed here: atomiks/tippyjs#1132 |
I have exactly the same issue after upgrading to next 13.4.11 (from next 12). downgrading to 13.4.9 fixed the issue for me. |
Hi, I believe the problem might be SWC. I've set up a playground example here I've tested in Next.js and running with For completeness sake, what happens is that: Gets minified into an empty object, and calling |
I ran into this issue and forked this repo with a temporary fix. I am filtering the plugins list and hard-coded the classNamePlugin in the two places it was being imported as a temporary workaround. I plan on switching back to this repo as soon as SWC stops doing what it's doing. I have no plans to support other bug fixes or changes, but use it if you want: https://github.com/aslakson/tippyjs-react
|
Same issue for me started with nextjs 13.4.10 |
I'll be fixed by swc-project/swc#7702 as indicated here: vercel/next.js#53151 (comment) |
This appears fixed for me now as of NextJS v13.4.15 Thank you team! |
I am getting the following error:
Looking into the tippy.js repo code, I saw that this line has to do with plugins. I am not loading any plugins with tippy, so I'm not sure why it is trying to call fn() on a plugin. I saw that the
@tippyjs-react
library does load some of its own plugins, so maybe there is an issue there?I wasn't having this issue prior, but started seeing it pop up now after I upgraded Next version 13.4.9 -> 13.4.10.
The text was updated successfully, but these errors were encountered: