Some of the most common errors in server side rendered React frameworks such as Next.js are the
document is not defined
or
window is not defined
errors. Why does it happen? This error typically appears when you or an installed package try to access the browser’s window objects directly in a page component, and it will throw this error because the window object is not yet available while a component is still mounting.
Say we have a sample index.js page in our Next.js application and try to access the browser localStorage like below; we’ll get the window is not defined error.
There are different approaches to resolving this error, one straightforward option is to simply employ react’s useEffect() hook to execute the code block that requires the browser’s window object, so that the code is only executed when the page component had been mounted.
Click to Copy
import { useEffect } from "react";
const Index = () => {
useEffect(() => {
window.localStorage.foo = "bar";
}, []);
return (
<h1>Welcome to my Blog!</h1>
export default Index;
Resolving in Next.js
If you’re using Next.js, there is another possible solution which is to convert the part of our code that requires the browser’s window to a standalone component and import it to our page component using Next.js dynamic import feature. Next’s dynamic import is a feature used to lazy-loading or dynamically load components on demand. However, it includes an additional ssr option that allows you to enable or disable server rendering when using it.
We can simply set the ssr value to false and will be able to load components or external packages that rely on the browser’s window or document.
Click to Copy
// components/SampleComponent.js
const SampleComponent = () => {
window.localStorage.foo = "bar";
return (
<h1>Welcome to my Blog!</h1>
export default SampleComponent;