New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't pass server component to PropTypes.node #407
Comments
Since when can a component be an async function? |
I guess since Next.js started supporting React server components. Assuming you're not looking for an exact date 😄 |
Actually, just noticed the same happens when rendering lazy components as children const MyLazyComponent = React.lazy(() => import('./Component')); |
I think we should also check that For the root of the issue, we might want to check that prop-types/factoryWithTypeCheckers.js Line 486 in 1c9c631
|
I’m pretty sure that hasn’t been released in react proper, and next.js just jumped the gun. I’ll try to look into it, though, since it’s likely that they’re all the same issue. |
Nesting a server component inside a client component that has
PropTypes.node
defined for itschildren
results in a warning:Reproduction: https://stackblitz.com/edit/stackblitz-starters-tn6djg?file=app%2Fpage.tsx
The text was updated successfully, but these errors were encountered: