Joseph
Joseph
Right, I aligned with other docs we have, but since I got to merge the FF solution, I think I can bring back the fade out.
Hi, I think we fixed this last week, didn't we?
Great! Thanks for the attention to detail. I'll go ahead an close the issue.
Hi, The problem is in your ThemeProvider, it does: ```js export default function ThemeProvider({ children }: Readonly) { const theme = useAppSelector(state => state.theme.theme); const [isClient, setIsClient] = useState(false); useEffect(()...
This is another issue entirely now. What HTML element is having the issue? It should be visible in the error overlay?
Doing the change within useEffect is the correct way. Hydration errors are found/triggered before the effects are run. The `isClient` check you are doing, is not good for SEO and...
I have bad news, somewhat... the hydration error, is happening because of `FontAwesomeIcon`... somehow in the server, it fails to load the icon, or something like that, and then in...
Not really, this page works now in LinkedIn Post Inspector. This project also uses Pages Router, not App Router. And it is a static output, export mode, application, which shouldn't...
Hi, we have reworked the docs for CSS https://nextjs.org/docs/app/getting-started/css
But if fetching fails/errors, there won't be data, and it won't be loading either.