Open
Conversation
zannager
added
integration: nextjs
brijeshb42
approved these changes
Nov 21, 2025
cianixru
approved these changes
Dec 18, 2025
guybendavid
approved these changes
Jan 11, 2026
|
Hi 👋 We’re currently blocked from upgrading to Next.js 16+ because of this issue, Since it’s already approved, I wanted to gently surface it in case it helps with prioritization. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Thank you for creating such a wonderful project.
This issue fixes #413.
I tested using
npm i --force, and it seemed to work fine with the Next.js 16 + Pigment CSS combination.Please review this PR quickly and release the new version.
Regards,