-
Notifications
You must be signed in to change notification settings - Fork 28
history: error boundary #1544
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
history: error boundary #1544
Conversation
This stack of pull requests is managed by Graphite. Learn more about stacking. |
Temporary Branch UpdateThe temporary branch has been updated with the latest changes. Below are the details:
Please use the above install command to update to the latest version. |
[Beta] Generated file diffTime updated: Thu, 06 Mar 2025 06:41:13 GMT Integration
File has changed Windows
File has changed Apple
File has changed |
cfe0841
to
2ef98e5
Compare
✅ Deploy Preview for content-scope-scripts ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I’ve tested this locally, and added the error in multiple components on the page, even inside an onclick for fun. The errors put in the components worked as intended, the onclick didn’t do anything but that’s to be expected 😄
Asana Task/Github Issue: https://app.asana.com/0/492600419927320/1209580861623842
Description
Testing Steps
npm run watch -- --page history -v
(run insidespecial-pages
)throw new Error('oops!')
in any component, such asspecial-pages/pages/history/app/components/App.jsx
Checklist
Please tick all that apply: