-
-
Notifications
You must be signed in to change notification settings - Fork 206
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
Warning: Prop id
did not match.(Server-Client)
#372
Comments
I am also getting this with Next.js 13 (app dir and client components) - using |
@alexnguyennz @canptleon do you have a sandbox or a link to the github project where this issue can be reproduced? |
@prabhuignoto I am also getting same error |
alternatively you can now disabled the auto id generation via a new prop |
Describe the bug
When I enter the page where I call the Chrono component, a warning comes up in the console.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Not getting this warning in console :)
Screenshots
If you need more information, please specify in the comments.
"@emotion/css": "11.5.0",
"@emotion/react": "11.0.0",
"@emotion/server": "11.4.0",
"@emotion/styled": "11.3.0",
"@rebass/grid": "6.1.0",
"react": "^18.2.0",
"next": "^13.1.4",
"react-chrono": "^2.1.2",
"typescript": "4.3.5"
Additional context
Hi, first of all, thank you very much for this library, it's really modern. I got a warning while using it in my nextjs project, do you know the solution? Warning disappears from console when Chrono component is not rendered.
The text was updated successfully, but these errors were encountered: