SolidJS 2.0 Beta: First-Class Async, Reworked Suspense and Deterministic Batching

2026-05-15 · Source: InfoQ · Field: Technology & Digital — Software Development & Engineering · Depth: Intermediate, short

Summary

SolidJS, a fine-grained reactive JavaScript framework, has released SolidJS 2.0 Beta, significantly overhauling its async handling, reactivity model, and developer experience. Key enhancements include first-class async support, allowing computations to return Promises and the reactive graph to manage suspension and resumption automatically, alongside a redesigned `Loading` component and `isPending(() => expr)` for pending states. Mutations now feature dedicated primitives like `action()` and `createOptimisticStore` for optimistic updates and data revalidation. The release also introduces derived state through function forms like `createSignal(fn)` and `createStore(fn)`, with microtask-batched updates and deterministic scheduling. Several breaking changes are included, such as the replacement of `Index` with `<Index>`, `createEffect` split into phases, and `onMount` replaced by `onSettled`.

Key takeaway

For Software Engineers building high-performance web applications with SolidJS, the 2.0 Beta introduces critical changes that simplify async operations and ensure deterministic state management. You should review the migration guides for 1.x and SolidStart to understand the breaking changes and adopt the new first-class async and mutation primitives. Embracing these changes will lead to more concise and coherent application designs, potentially reducing the need for `createEffect` in many scenarios.

Key insights

SolidJS 2.0 introduces first-class async and deterministic batching for a more consistent and coherent reactive programming model.

Principles

• Async operations can be directly integrated into the reactive graph.
• Deterministic batching ensures consistent state updates.
• Optimistic updates improve perceived performance.

Method

SolidJS 2.0's approach involves passing Promises directly to `createMemo`, using `action()` for mutations, and leveraging `createOptimisticStore` for optimistic UI updates, with microtask-batched updates ensuring deterministic state changes.

In practice

• Pass Promises directly into `createMemo` for async handling.
• Use `action()` for server writes and data revalidation.
• Implement optimistic UI updates with `createOptimisticStore`.

Topics

• SolidJS 2.0 Beta
• First-Class Async
• Reworked Suspense
• Deterministic Batching
• Optimistic Updates

Code references

• solidjs/solid

Best for: Software Engineer

Related on AIssential

• Stochastic convergence of parallel asynchronous adaptive first-order methods — New asynchronous adaptive first-order methods achieve O(1/sqrt{t}) convergence on non-convex functions in stochastic settings.
• Postgres is now async by Default — PostgreSQL now defaults to an asynchronous worker-based I/O method, enhancing performance and consistency across platforms.
• Concurrency Foundations For FastHTML — Implement concurrency in Starlette apps using database queues, threads, or async for non-blocking background tasks.
• Rescaled Asynchronous SGD: Optimal Distributed Optimization under Data and System Heterogeneity — Rescaled ASGD uses worker-specific stepsize rescaling to correct objective bias in heterogeneous asynchronous distributed learning.
• TypeORM Reaches 1.0 After Nearly a Decade, Signalling Renewed Maintenance — TypeORM 1.0 confirms renewed maintenance and modernizes its core, enhancing security and developer features.
• Clipping Makes Distributed and Federated Asynchronous SGD Robust to Stragglers — Gradient clipping theoretically justifies ASGD robustness by removing maximum delay dependence, even with heavy-tailed noise.

Open in AIssential →

Editorial summary, takeaway, and curation by AIssential. Original article published by InfoQ.