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

Feature/error boundaries #48

Open
wants to merge 4 commits into
base: main
Choose a base branch
from
Open

Feature/error boundaries #48

wants to merge 4 commits into from

Conversation

mrtag23
Copy link
Collaborator

@mrtag23 mrtag23 commented Oct 21, 2024

No description provided.

@mrtag23 mrtag23 requested a review from asgorobets October 21, 2024 15:53
Copy link

vercel bot commented Oct 21, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
nextjs-contentful ✅ Ready (Inspect) Visit Preview 💬 Add feedback Nov 15, 2024 6:55pm

@@ -0,0 +1,41 @@
'use client';
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Well, it turns out client boundaries don't catch server errors, maybe this functionality can be written using try/catch and async components, but client error boundaries are not useful =)
Screenshot 2024-11-15 at 1 51 22 PM

See my chat with v0 for some ideas explored

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Add error boundary to component renderer to prevent whole page from failing when one component fails
2 participants