Skip to content
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

Add note suggesting to use <Suspense> instead of <ClientOnly> #159

Merged

Conversation

tom-sherman
Copy link
Contributor

@tom-sherman tom-sherman commented Feb 2, 2023

I think the end goal should be to deprecate ClientOnly, but that would require a couple of things:

  • Wide enough adoption of React 18 and streaming SSR in remix apps (haven't researched this)
  • Better error handling. Right now this suspense technique logs the error on the server, which isn't ideal for Remix client-only components.

@tom-sherman tom-sherman changed the title Add note suggesitng to use <Suspense> instead of ClientOnly Add note suggestng to use <Suspense> instead of ClientOnly Feb 2, 2023
@sergiodxa sergiodxa changed the title Add note suggestng to use <Suspense> instead of ClientOnly Add note suggesting to use <Suspense> instead of <ClientOnly> Feb 3, 2023
README.md Outdated Show resolved Hide resolved
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants