Your outie uses React with grace
Your outie already got bitten by useEffect()
Your outie once caught an exception in <ErrorBoundary>
Your outie recommends Vite, but it must be used with React Router in framework mode
Your outie already got bitten by useEffect()
Your outie once caught an exception in <ErrorBoundary>
Your outie recommends Vite, but it must be used with React Router in framework mode
February 19, 2025 at 10:51 AM
Your outie uses React with grace
Your outie already got bitten by useEffect()
Your outie once caught an exception in <ErrorBoundary>
Your outie recommends Vite, but it must be used with React Router in framework mode
Your outie already got bitten by useEffect()
Your outie once caught an exception in <ErrorBoundary>
Your outie recommends Vite, but it must be used with React Router in framework mode
👀 React on v19
A subtle but interesting behavior change is explained here
Seems like now it will "fail-fast" and bail out on the first error, while previously it "aggregated" errors
andrei-calazans.com/posts/react-...
A subtle but interesting behavior change is explained here
Seems like now it will "fail-fast" and bail out on the first error, while previously it "aggregated" errors
andrei-calazans.com/posts/react-...
November 12, 2025 at 12:01 PM
👀 React on v19
A subtle but interesting behavior change is explained here
Seems like now it will "fail-fast" and bail out on the first error, while previously it "aggregated" errors
andrei-calazans.com/posts/react-...
A subtle but interesting behavior change is explained here
Seems like now it will "fail-fast" and bail out on the first error, while previously it "aggregated" errors
andrei-calazans.com/posts/react-...
if you haven't been following the work on @solidjs.com 2.0:
- createAsync throws instead of returning undefined 🎉
- Resetting an ErrorBoundary refetches errored createAsyncs
- Suspense only shows its fallback once. On re-suspend it shows stale data (no Transition!)
+ much more
i'm very excited 😄
- createAsync throws instead of returning undefined 🎉
- Resetting an ErrorBoundary refetches errored createAsyncs
- Suspense only shows its fallback once. On re-suspend it shows stale data (no Transition!)
+ much more
i'm very excited 😄
February 17, 2025 at 10:34 AM
if you haven't been following the work on @solidjs.com 2.0:
- createAsync throws instead of returning undefined 🎉
- Resetting an ErrorBoundary refetches errored createAsyncs
- Suspense only shows its fallback once. On re-suspend it shows stale data (no Transition!)
+ much more
i'm very excited 😄
- createAsync throws instead of returning undefined 🎉
- Resetting an ErrorBoundary refetches errored createAsyncs
- Suspense only shows its fallback once. On re-suspend it shows stale data (no Transition!)
+ much more
i'm very excited 😄
Remember: not every component needs an ErrorBoundary 💡
December 1, 2025 at 11:38 AM
Remember: not every component needs an ErrorBoundary 💡
The structure I’ve been using lately is generally:
`
export const Component
cost query = useSuspenseQuery
export default (
Layout
ErrorBoundary
Suspense
Component
`
Normally a fan of early returns, but for some reason this has stuck.
`
export const Component
cost query = useSuspenseQuery
export default (
Layout
ErrorBoundary
Suspense
Component
`
Normally a fan of early returns, but for some reason this has stuck.
March 14, 2025 at 1:04 AM
The structure I’ve been using lately is generally:
`
export const Component
cost query = useSuspenseQuery
export default (
Layout
ErrorBoundary
Suspense
Component
`
Normally a fan of early returns, but for some reason this has stuck.
`
export const Component
cost query = useSuspenseQuery
export default (
Layout
ErrorBoundary
Suspense
Component
`
Normally a fan of early returns, but for some reason this has stuck.
This is not at all a big deal, but why is React still using class components for error boundaries?
I feel like every app has this in it by now, why not just make an official version of it
I feel like every app has this in it by now, why not just make an official version of it
April 3, 2025 at 6:50 PM
This is not at all a big deal, but why is React still using class components for error boundaries?
I feel like every app has this in it by now, why not just make an official version of it
I feel like every app has this in it by now, why not just make an official version of it
Wait, there's really no way to write a React error boundary with a functional component? I need to go back to `class ErrorBoundary extends React.Component` and implement `static getDerivedStateFromError`? @danabra.mov save me
March 13, 2026 at 6:03 PM
Wait, there's really no way to write a React error boundary with a functional component? I need to go back to `class ErrorBoundary extends React.Component` and implement `static getDerivedStateFromError`? @danabra.mov save me
⚛️ Day 35 #100DaysOfCode #React Error Boundaries
If you want a shared fallback UI for API failures, you need to surface the error back into the render phase.
Pattern:
1️⃣ catch async error
2️⃣ store it in state
3️⃣ throw it during render → ErrorBoundary can now catch it
If you want a shared fallback UI for API failures, you need to surface the error back into the render phase.
Pattern:
1️⃣ catch async error
2️⃣ store it in state
3️⃣ throw it during render → ErrorBoundary can now catch it
November 16, 2025 at 3:18 AM
⚛️ Day 35 #100DaysOfCode #React Error Boundaries
If you want a shared fallback UI for API failures, you need to surface the error back into the render phase.
Pattern:
1️⃣ catch async error
2️⃣ store it in state
3️⃣ throw it during render → ErrorBoundary can now catch it
If you want a shared fallback UI for API failures, you need to surface the error back into the render phase.
Pattern:
1️⃣ catch async error
2️⃣ store it in state
3️⃣ throw it during render → ErrorBoundary can now catch it
the nice thing about React (which wasn’t acked in the post) is that it gives you a first-class primitive to catch these — <ErrorBoundary>. in Next it’s additionally exposed by convention as error.js in any route or subroute. it does suck that people aren’t aware it exists, and docs could be better
June 13, 2025 at 10:50 PM
the nice thing about React (which wasn’t acked in the post) is that it gives you a first-class primitive to catch these — <ErrorBoundary>. in Next it’s additionally exposed by convention as error.js in any route or subroute. it does suck that people aren’t aware it exists, and docs could be better
I don’t get why you would use <ErrorBoundary> when you can simply not have errors
September 3, 2024 at 5:53 PM
I don’t get why you would use <ErrorBoundary> when you can simply not have errors
Data fetching in React can get tricky as your apps scale. And in this handbook, Tapas walks you through modern data fetching strategies. You'll first review useEffect, then learn how to use Suspense, the new use() API, and ErrorBoundary.
www.freecodecamp.org/news/the-mod...
www.freecodecamp.org/news/the-mod...
February 14, 2026 at 5:01 AM
Data fetching in React can get tricky as your apps scale. And in this handbook, Tapas walks you through modern data fetching strategies. You'll first review useEffect, then learn how to use Suspense, the new use() API, and ErrorBoundary.
www.freecodecamp.org/news/the-mod...
www.freecodecamp.org/news/the-mod...
They used next-intl for localization, added structured data with custom fields, and even wrapped the #StoryblokServerComponent in Suspense and #ErrorBoundary for added stability.
It’s live with Live Editing, integrated #FriendlyCaptcha, and deployed on #Vercel.
It’s live with Live Editing, integrated #FriendlyCaptcha, and deployed on #Vercel.
June 13, 2025 at 9:00 AM
They used next-intl for localization, added structured data with custom fields, and even wrapped the #StoryblokServerComponent in Suspense and #ErrorBoundary for added stability.
It’s live with Live Editing, integrated #FriendlyCaptcha, and deployed on #Vercel.
It’s live with Live Editing, integrated #FriendlyCaptcha, and deployed on #Vercel.
Data fetching in React can get tricky as your apps scale. And in this handbook, Tapas walks you through modern data fetching strategies. You'll first review useEffect, then learn how to use Suspense, the new use() API, and ErrorBoundary.
www.freecodecamp.org/news/the-mod...
www.freecodecamp.org/news/the-mod...
The Modern React Data Fetching Handbook: Suspense, use(), and ErrorBoundary Explained
Most React developers don’t break the data fetching process all at once. It usually degrades gradually, slowly. Traditionally, you may have used a useEffect here, a loading flag there, and an error…
www.freecodecamp.org
June 8, 2026 at 4:01 AM
Data fetching in React can get tricky as your apps scale. And in this handbook, Tapas walks you through modern data fetching strategies. You'll first review useEffect, then learn how to use Suspense, the new use() API, and ErrorBoundary.
www.freecodecamp.org/news/the-mod...
www.freecodecamp.org/news/the-mod...
there's a similar confusion in react though, so not saying react is perfect here. for example if upperPhrase() as a function call errors here, this is not the error boundary that is shown, the parent boundary is:
<ErrorBoundary>
<Message text={upperPhrase()} />
</ErrorBoundary>
<ErrorBoundary>
<Message text={upperPhrase()} />
</ErrorBoundary>
September 10, 2025 at 7:11 PM
there's a similar confusion in react though, so not saying react is perfect here. for example if upperPhrase() as a function call errors here, this is not the error boundary that is shown, the parent boundary is:
<ErrorBoundary>
<Message text={upperPhrase()} />
</ErrorBoundary>
<ErrorBoundary>
<Message text={upperPhrase()} />
</ErrorBoundary>
All routes are existing "client routes" by default as they are today. Exporting a ServerComponent instead of default switches it to a "server route". All other component exports ErrorBoundary, Layout, etc also become "server components" when doing so. It shifts the *entire* route to the server.
May 16, 2025 at 5:21 PM
All routes are existing "client routes" by default as they are today. Exporting a ServerComponent instead of default switches it to a "server route". All other component exports ErrorBoundary, Layout, etc also become "server components" when doing so. It shifts the *entire* route to the server.
🔍 Vulnerability Spotlight | Part 2/3
⚠️ CVE-2026-93981
hono before 4.13.7 fails to HTML-escape plain strings rendered by hono/jsx as a child or fallback of Suspense, as a string child of ErrorBoundary a...
⚠️ CVE-2026-93981
hono before 4.13.7 fails to HTML-escape plain strings rendered by hono/jsx as a child or fallback of Suspense, as a string child of ErrorBoundary a...
September 20, 2026 at 11:39 AM
🔍 Vulnerability Spotlight | Part 2/3
⚠️ CVE-2026-93981
hono before 4.13.7 fails to HTML-escape plain strings rendered by hono/jsx as a child or fallback of Suspense, as a string child of ErrorBoundary a...
⚠️ CVE-2026-93981
hono before 4.13.7 fails to HTML-escape plain strings rendered by hono/jsx as a child or fallback of Suspense, as a string child of ErrorBoundary a...
- Things like ErrorBoundary and Suspense that invert control flow are also fairly easy to model
- All of this composes quite nicely
- All of this composes quite nicely
November 6, 2024 at 11:48 PM
- Things like ErrorBoundary and Suspense that invert control flow are also fairly easy to model
- All of this composes quite nicely
- All of this composes quite nicely
bfcacheのErrorBoundaryとかの問題が起きなくなったんだ "fix: prevent fetch abort errors propagating to user error boundaries" https://github.com/vercel/next.js/pull/86277
December 27, 2025 at 1:21 AM
bfcacheのErrorBoundaryとかの問題が起きなくなったんだ "fix: prevent fetch abort errors propagating to user error boundaries" https://github.com/vercel/next.js/pull/86277
This weekend I've build 2 packages for django-components
- One for icons from HeroIcons.com
- The other for "ErrorBoundary" component
Still blocked by a few more PRs on django-components, but will ship it as soon as possible.
- One for icons from HeroIcons.com
- The other for "ErrorBoundary" component
Still blocked by a few more PRs on django-components, but will ship it as soon as possible.
January 5, 2025 at 5:53 PM
This weekend I've build 2 packages for django-components
- One for icons from HeroIcons.com
- The other for "ErrorBoundary" component
Still blocked by a few more PRs on django-components, but will ship it as soon as possible.
- One for icons from HeroIcons.com
- The other for "ErrorBoundary" component
Still blocked by a few more PRs on django-components, but will ship it as soon as possible.
New PR: ALF ErrorScreen (#9912)
ALF ErrorScreen by mozzius · Pull Request #9912 · bluesky-social/social-app
Stacked on #9911
New icon to match designs
Adjust spacing
Add "try again" button to ErrorBoundary which reloads the app
Move to #/components
github.com
February 20, 2026 at 11:07 AM
New PR: ALF ErrorScreen (#9912)
The states are URL params, no handler code: ?mock_delay=3000 shows your Suspense fallback for real, ?mock_status=500 fires the ErrorBoundary, ?mock_chaos=0.5 gives Retry something to recover from (ours took 2 tries). One-click backend: https://mockbird.mockbird.workers.dev/app#new=ecommerce
August 4, 2026 at 9:48 AM
The states are URL params, no handler code: ?mock_delay=3000 shows your Suspense fallback for real, ?mock_status=500 fires the ErrorBoundary, ?mock_chaos=0.5 gives Retry something to recover from (ours took 2 tries). One-click backend: https://mockbird.mockbird.workers.dev/app#new=ecommerce
How would you feel if your pre-built step components snapped together like LEGO but left users staring at a frozen screen when the validation library throws a silent error? Have you tried wrapping each step in a React ErrorBoundary with a toast fallback?
June 8, 2026 at 8:09 PM
How would you feel if your pre-built step components snapped together like LEGO but left users staring at a frozen screen when the validation library throws a silent error? Have you tried wrapping each step in a React ErrorBoundary with a toast fallback?