Error: Importing a component that needs useState. It only works in a Client Component, but none of its parents are marked with use client, so they're Server Components by default.
Shivan M.
—When using useState
in a component in Next.js 13, you might encounter the following error:
You're importing a component that needs useState. It only works in a Client Component, but none of its parents are marked with "use client", so they're Server Components by default.
This error occurs when using the app
directory. By default, in Next.js 13, components are marked as Server Components. This means that the HTML is compiled on the server and sent to the client. Server Components shouldn’t contain any code that uses browser-specific APIs, or hooks that are specifically intended for client-side usage (like useState
).
To resolve this error, you can use the use client
directive to mark components as Client Components.
The component below would result in the error in question:
import { useState } from "react"; export default function MyComponent() { const [state, setState] = useState(""); return <></>; }
By adding the use client
directive, we resolve the error:
"use client"; import { useState } from "react"; export default function MyComponent() { const [state, setState] = useState(""); return <></>; }
If you want to use a component marked as a Client Component in a Server Component (for example, a third-party library), export the component from the lib
folder at the same level as the app
directory.
// lib/third-party-component.js "use client"; export * from "@some/library";
Then, in your Server Component:
import { Component } from "../lib/third-party-component"; export default function Page() { return ( // use your component ) }
Tasty treats for web developers brought to you by Sentry. Get tips and tricks from Wes Bos and Scott Tolinski.
SEE EPISODESConsidered “not bad” by 4 million developers and more than 100,000 organizations worldwide, Sentry provides code-level observability to many of the world’s best-known companies like Disney, Peloton, Cloudflare, Eventbrite, Slack, Supercell, and Rockstar Games. Each month we process billions of exceptions from the most popular products on the internet.
Here’s a quick look at how Sentry handles your personal information (PII).
×We collect PII about people browsing our website, users of the Sentry service, prospective customers, and people who otherwise interact with us.
What if my PII is included in data sent to Sentry by a Sentry customer (e.g., someone using Sentry to monitor their app)? In this case you have to contact the Sentry customer (e.g., the maker of the app). We do not control the data that is sent to us through the Sentry service for the purposes of application monitoring.
Am I included?We may disclose your PII to the following type of recipients:
You may have the following rights related to your PII:
If you have any questions or concerns about your privacy at Sentry, please email us at compliance@sentry.io.
If you are a California resident, see our Supplemental notice.