Add client-only to mark everything as client components
#1981
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This should improve the error messages when using Headless UI in a Next.js 13+ repo instead of getting a cryptic error message that `createContext` doesn't exist.
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
RobinMalfait
deleted the
fix/improve-error-messages-for-react-server-components
branch
|
After this change headlessui doesn't work with nextjs 12 + ssr. |
|
I only see your comment now @tonypizzicato, the error should already occur when using Headless UI components in non-client only components (aka Server Components) without the |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This should improve the error messages when using Headless UI in a Next.js 13+ repo instead of getting a cryptic error message that
createContextdoesn't exist.