question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Warning: Prop `id` did not match.

See original GitHub issue

Hello, I’m rendering React 16 on client and server(SSR) with new function React.hydrate(). And console throw Warning message: Warning: Prop id did not match. Server: "starGrad239537257264089" Client: "starGrad357747279155326"

This is the only problem with this component. Thank’s a lot!

Issue Analytics

  • State:open
  • Created 4 years ago
  • Reactions:9
  • Comments:12

github_iconTop GitHub Comments

16reactions
BodyaNKcommented, Sep 23, 2020

If you’re using Next js with server side rendering, you need to import StarRatings from “react-star-ratings” dynamically with no ssr. For example:

import dynamic from "next/dynamic";
const StarRatings = dynamic(() => import("react-star-ratings"), {
  ssr: false,
});

For me it’s work. Hope this will help.

5reactions
robin-thomascommented, Jul 5, 2019
Read more comments on GitHub >

github_iconTop Results From Across the Web

Recharts - Warning: Prop id did not match. Server: #12863
This is a generic Next.js warning that happens when the DOM in the client does not exactly match the DOM that was rendered...
Read more >
how to resolve "Prop `id` did not match. Server: "react-tabs-30 ...
This error means that something on the server is different from the Client. This can happen if the client does a re-render. For...
Read more >
“react-select-3-live-region”の原因と対処法 - weev【ウィーブ】
Prop `id` did not match. Server: “react-select-17-live-region” Client: “react-select-3-live-region”の原因と対処法 · 1 エラー内容. 1.1 コード例( ...
Read more >
Prop `id` did not match. Server: "reactHubspotForm4" Client ...
I have embedded the Hubspot script in my Next.js project. But now every time I refresh the page locally I get the error...
Read more >
react-bootstrap-ssr-id-bug - CodeSandbox
Console should log: Warning: Prop id did not match. Server: "react-aria-1-tab-home" Client: "react-aria-2-tab-home" despite using SSRProvider.
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found