digestweb.dev
Propose a News Source
Support usSponsor
🤝
Curated byFRSOURCE

digestweb.dev

Your essential dose of webdev and AI news, handpicked.

Advertisement

Want to reach web developers daily?

Advertise with us ↗

Back to Daily Feed

SolidJS Signals 2.0 RC.16: Reactivity & Error Handling Fixes

Originally published on SolidJS Releases

View Original Article
Share this article:
SolidJS Signals 2.0 RC.16: Reactivity & Error Handling Fixes

Summary & Key Takeaways ​

  • Synchronous throws from async iterators are now routed to the owning memo's error handling.
  • StatusError message formatting is now best-effort to prevent replacing original errors.
  • Loading boundary behavior is fixed, ensuring fallbacks are not prematurely shown.
  • Effects and memos catching NotReadyError from async derived stores now re-run when the store's flight lands.
  • Signal writes from onCleanup during transition landings no longer leave the transaction parked.
  • Writes are now allowed in cleanups during teardown, preventing reactivity halts in development.

Our Commentary ​

More SolidJS 2.0 RC goodness, this time for signals. The fixes around async error handling and Loading boundaries are crucial for building robust applications. I've definitely run into tricky situations with async state, so seeing these kinds of stability improvements is reassuring. Allowing writes in cleanups during teardown also feels like a necessary correction for more predictable reactivity.

View Original Article
Share this article:
RSS Atom JSON Feed
© 2026 digestweb.dev — brought to you by  FRSOURCE