1 of 2 React Hydration — Error 1 of 3 errors in Admin view: Unhandled Runtime Error: Error: Hydration failed because the initial UI does not match what was rendered on the server.

[lloydchang]

Describe the bug
1 of 2 React Hydration — Error 1 of 3 errors in Admin view: Unhandled Runtime Error: Error: Hydration failed because the initial UI does not match what was rendered on the server.

To Reproduce
Steps to reproduce the behavior:

1. Go to Admin view

Expected behavior
Error message without the stack trace.

Screenshots
1 of 2 React Hydration — Error 1 of 3 errors in Admin view: Unhandled Runtime Error: Error: Hydration failed because the initial UI does not match what was rendered on the server.

1 of 3 unhandled errors

Unhandled Runtime Error
Error: Hydration failed because the initial UI does not match what was rendered on the server.

See more info here: https://nextjs.org/docs/messages/react-hydration-error

Call Stack
throwOnHydrationMismatch
node_modules/react-dom/cjs/react-dom.development.js (12507:0)
tryToClaimNextHydratableInstance
node_modules/react-dom/cjs/react-dom.development.js (12535:0)
updateHostComponent
node_modules/react-dom/cjs/react-dom.development.js (19902:0)
beginWork
node_modules/react-dom/cjs/react-dom.development.js (21618:0)
HTMLUnknownElement.callCallback
node_modules/react-dom/cjs/react-dom.development.js (4164:0)
Object.invokeGuardedCallbackDev
node_modules/react-dom/cjs/react-dom.development.js (4213:0)
invokeGuardedCallback
node_modules/react-dom/cjs/react-dom.development.js (4277:0)
beginWork$1
node_modules/react-dom/cjs/react-dom.development.js (27451:0)
performUnitOfWork
node_modules/react-dom/cjs/react-dom.development.js (26557:0)
workLoopSync
node_modules/react-dom/cjs/react-dom.development.js (26466:0)
renderRootSync
node_modules/react-dom/cjs/react-dom.development.js (26434:0)
performConcurrentWorkOnRoot
node_modules/react-dom/cjs/react-dom.development.js (25738:0)
workLoop
node_modules/scheduler/cjs/scheduler.development.js (266:0)
flushWork
node_modules/scheduler/cjs/scheduler.development.js (239:0)
MessagePort.performWorkUntilDeadline
node_modules/scheduler/cjs/scheduler.development.js (533:0)

Desktop (please complete the following information):

• OS: Mac
• Browser: Chrome
• Version: Version 114.0.5735.198 (Official Build) (x86_64)

Additional context
Relates to
#134
#360
#361

[lloydchang]

Hi @theGaryLarson @Komal914 @sijin-raj @GuillermoFloresV

If @theGaryLarson and/or @Komal914 are looking for additional issues to solve, I reported:
• #359
• #360
• #361

Thank you!

[GuillermoFloresV]

Hi Lloyd, thanks for this. We can consolidate the issues into a single one since it's all caused by a single hydration issue.

[lloydchang]

Hi @GuillermoFloresV

It depends.

. 1. From the end-user perspective, it's three issues for three error messages.

. 2. From the developer's perspective, it's one pull request with one fix for three issues.

The consolidation could be done by the developer when fixing the issue.

Whereas the consolidation would not be done by the end-user who reported the issue.

. 3. There could be a triage team between the end-user and developer who consolidate the issue, but is there a triage team?

Thanks!

By the way, @theGaryLarson is looking for your direction on which https://github.com/freeCodeCamp/classroom issues to work on.

Can @theGaryLarson work on these React, Hydration, and Boundary issues?
• #359
• #360
• #361

Thanks again!

[lloydchang]

Related information from
https://codedayorg.slack.com/archives/C05E350DQH4/p1688894693666219?thread_ts=1688836862.909659

@Komal Kaur @sijin @Gary Larson

If I were in your shoes, below is how I would go about it:

•  Before considering a solution, I would seek to understand the problem clearly first:

  • Before skipping ahead to the solution phase and diving into the codebase such as error.js, which is probably at shallower abstraction layers closer to the surface and the user interface…

1. First, I would want clarity about the error messages and their contexts, which are probably at deeper abstraction layers below the surface and user interface.

For example:

Error messages 1 and 2:
The hints from the messages may help, specifically the keyword Hydration

Error message 3:
The hints from the error message may help, specifically the keyword Boundary

Error messages 1 and 2:

Unhandled Runtime Error

Error: Hydration failed because the initial UI does not match what was rendered on the server.

See more info here: https://nextjs.org/docs/messages/react-hydration-error

Google search of:

Error: Hydration failed because the initial UI does not match what was rendered on the server.

Points to

https://stackoverflow.com/questions/71706064/react-18-hydration-failed-because-the-initial-ui-does-not-match-what-was-render

I have been experiencing the same problem lately with NextJS and i am not sure if my observations are applicable to other libraries. I had been wrapping my components with an improper tag that is, NextJS is not comfortable having a p tag wrapping your divs, sections etc so it will yell "Hydration failed because the initial UI does not match what was rendered on the server". So I solved this problem by examining how my elements were wrapping each other.

Which points to

facebook/react#24519 (comment)

This seems to be expected behavior? SSR cannot work with improper tag nesting as per the HTML spec, the browser's parser won't accept it, and the whole point of SSR is to have the browser parse the initial document structure for you without using any JS. Client side rendering can work with improper tag nesting because the DOM apis do allow creating these invalid nestings "by hand" (with document.createElement, appendChild, etc.).

There is no way to create a raw HTML document that nests a

directly inside a

using static markup, so there's no way to do it with SSR.

So this situation is a warning for client side rendering, an error for SSR, and a warning for hydration; but the only way to continue the "hydration" is to blast away all of the DOM so far because it will be wrong due to invalid nesting.

In error messages 1 and 2, a keyword is Hyrdation.

The referenced web link in error messages 1 and 2 is:

https://nextjs.org/docs/messages/react-hydration-error

Text content does not match server-rendered HTML

Why This Error Occurred

While rendering your application, there was a difference between the React tree that was pre-rendered (SSR/SSG) and the React tree that rendered during the first render in the Browser. The first render is called Hydration which is a feature of React.

This can cause the React tree to be out of sync with the DOM and result in unexpected content/attributes being present.

Possible Ways to Fix It

In general, this issue is caused by using a specific library or application code that is relying on something that could differ between pre-rendering and the browser.

An example of this is using window in a component's rendering.

Another example:

Invalid HTML may cause hydration mismatch such as div inside p.

Error message 3 of 3:

Unhandled Runtime Error

Error: There was an error while hydrating. Because the error happened outside of a Suspense Boundary, the entire root will switch to client rendering.

In error message 3, a keyword is Boundary.

Hence a Google Search for boundary in React leads to:

https://react.dev/reference/react/Component#catching-rendering-errors-with-an-error-boundary

Catching rendering errors with an error boundary

By default, if your application throws an error during rendering, React will remove its UI from the screen. To prevent this, you can wrap a part of your UI into an error boundary. An error boundary is a special component that lets you display some fallback UI instead of the part that crashed—for example, an error message.

https://nextjs.org/docs/pages/building-your-application/configuring/error-handling

Handling Client Errors

React Error Boundaries is a graceful way to handle a JavaScript error on the client so that the other parts of the application continue working. In addition to preventing the page from crashing, it allows you to provide a custom fallback component and even log error information.

To use Error Boundaries for your Next.js application, you must create a class component ErrorBoundary and wrap the Component prop in the pages/_app.js file. This component will be responsible to:

• Render a fallback UI after an error is thrown
• Provide a way to reset the Application's stat
• Log error information

[Ismailtlem]

How to get to the admin view @lloydchang @GuillermoFloresV please guys ? I don't seem to find it

[Komal914]

@Ismailtlem Hey! You need to update your role as admin inside Prisma Studio. Prisma Studio is on port 5555 locally

[GuillermoFloresV]

To add to Komal's comment, you have to have Prisma studio running on it's own terminal. The command is npx prisma studio

[lloydchang]

#398
lgtm as a good enough solution because Admin view isn't intended for Search Engine Optimization (SEO).
I don't know why the errors were happening in the first place, but it may not matter if Server Side Rendering (SSR) can be disabled for the Admin view.

[lloydchang]

This error no longer happens after #401

[lloydchang]

Please contact @GuillermoFloresV if you have further questions about this. Thanks!