-
Notifications
You must be signed in to change notification settings - Fork 628
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
Render issues on Next.js 13.5.4 after upgrading from 13.4.12 #501
Comments
Ya it works fine when I am just running |
Same thing happening here! |
Same issue here. |
linked with nextjs update to 13.5.4 (13.5.3 works fine) |
Any update on this issue? Kind of a big problem. |
I tracked it down to a specific commit that broke it. It has something to do with the SWC minifier. If you set
Workaround |
@camcamcamcam I've had |
I think it is because they changed the defaults for the SWC minifier in 13.5.4, from the default of I'm honestly not sure why this affects react-paginate, but it does. It at least does explains why it only happens in builds. |
Does it affect for performance? since it is SWC thing |
@lutfi-haslab Not in anyway that I have noticed in production, since it is still being minified, just using the pre v13 minifier. The only difference I have noticed, or at least can measure, is that the build take ever so slightly longer. |
I have this issue in production too. Kind of a big problem for my company. Next: 13.5.4 |
I faced same issue when I updated Next version to 13.5.4. As a temporary solution, I downgraded Next.js to the previous version. However, this is not an ideal solution. I would appreciate it if the issue could be fixed to work correctly with the new version. |
I have same issue :) |
Having the same issue. Had to use this workaround |
I was able to show it again after downgrade to next 13.5.2 and react-paginate 8.1.4 |
I was having the same issue, and just upgrade the next.js version to 15.5.5 (latest version) solved my issue. |
It's still broken for v15.5.5 and |
which react-paginate version? still broken here like @JavierMartinz ^ |
I just updated to [email protected], and trying with both [email protected] and [email protected], and can confirm it is still broken. |
Sorry I forgot to send my specs. Versions: Config: |
Same issue in 13.5.6 swcMinify: false |
same issue |
Same issue |
Still exists on [email protected] |
Disabling SWC Minifer will not be an option in the next major version. Please report any issues you may be experiencing to https://github.com/vercel/next.js/issues For now it works by disabling the "swcMinify" but it will be removed by Next in the future. |
Same error |
This actually works, but I don't know if it affects performance the way nextjs described. |
same issue |
Same Issue. I hope it is resolved as soon as possible |
This is working again for me for nextjs >= 14.0.2 😀 |
same 🙌 |
facing the same issue. |
I got the same problem after installing "framer-motion", but after updating next >= 14.0.2 all worked correctly |
Updating to 14.0.4 solved the problem for me. |
adding swcMinify: false in next.config.js works for me. |
Bumped up my version of Next.js to silence a vulnerability notice, and after doing so react-paginate no longer works correctly. Getting around it for now by locking my version to 13.4.12, but not a fan of this solution.
Expected behaviour (on 13.4.12):
What happens (on 13.5.4):
Here is the JS of one of the pages that has pagination, if that helps. All instances of ReactPaginate on this site are experiencing this.
The text was updated successfully, but these errors were encountered: