Fix Prop nonce did not match error #223
Closed
Conversation
This file contains 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
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Enalmada
changed the title
Prop nonce did not match. errorProp nonce did not match.` error
Enalmada
changed the title
Prop nonce did not match.` error
|
UP facing the same issue ! |
|
Got this issue |
|
Fixed in #262 |
|
Also facing after upgrade to 0.3.0 |
|
@pacocoursey I think you missed to include this change in 0.3 release https://www.unpkg.com/next-themes@0.3.0/dist/index.js |
|
No, it was merged after. #262 hasn't been released yet, but the issue is fixed in the source code. |
|
@pacocoursey could you do a release with it pretty please? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
I am getting
Warning: Prop `nonce` did not match. Server: "" Client: "rj3157e91u"despite passing in a nonce.When trying to search for why this error is happening I found this: https://github.com/kentcdodds/nonce-hydration-issues
TLDR: Apparently the browser, for security reasons, clears the nonce the way that next-themes is creating script tag. This leads to a mismatch, causing the warning.
I believe this fixes: #218
I have created a build with this fix for testing and it seems to work:
"@enalmada/next-themes": "^0.2.3",