--- title: Solid 2.0 hits Release Candidate with first-class async... description: Solid 2.0 has reached Release Candidate status with async support built directly into its reactive core. Computations can now return promises directly, letting... canonical: https://daily.dev/posts/solid-2-0-hits-release-candidate-with-first-class-async-support-fwnxbelqc twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Solid 2.0 hits Release Candidate with first-class async support | daily.dev og:description: Solid 2.0 has reached Release Candidate status with async support built directly into its reactive core. Computations can now return promises directly, letting... og:url: https://daily.dev/posts/solid-2-0-hits-release-candidate-with-first-class-async-support-fwnxbelqc og:image: https://api.daily.dev/og/posts/fWNxbelQc.png og:image:alt: Solid 2.0 hits Release Candidate with first-class async support og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Solid 2.0 hits Release Candidate with first-class async support **[Collections](https://daily.dev/sources/collections)** · 3 min read · 1 upvotes · 0 comments ## Summary Solid 2.0 has reached Release Candidate status with async support built directly into its reactive core. Computations can now return promises directly, letting the dependency graph suspend and resume around them without manual loading-state wiring or extra libraries. The release also adds optimistic mutations for updating UI before server responses arrive, and ships a reactive core rebuilt from scratch rather than patched onto the previous one. ## Content Cursor has migrated its editor codebase off Solid.js and onto React. The news came from Cursor engineer and former React Core Team member Lauren Tan, who pointed to some signals-based performance footguns, but the bigger reason was that coding agents simply write more predictable React code once a codebase gets complex. Basically: the models know React better, so React wins by default. The timing is rough. This landed the same week Solid.js shipped its Solid 2.0 release candidate, the biggest rework in the framework's history. It's not a small update, either — first-class async support (computations can now return promises, and the reactive graph suspends and resumes on its own), a Suspense replacement called Loading, isPending() for tracking background refreshes, and new mutation primitives like action() and createOptimisticStore. Solid creator Ryan Carniato didn't hide how he felt about the Cursor news. In a public post, he thanked Cursor for genuinely making Solid 2.0 possible — "the credits and the IDE have been the pillarstone of my work the last 7 months" — but also aired some real frustration. He said he didn't even know Cursor was using Solid internally until years in, and when he tried to get Cursor's team into the Solid Discord to talk things through, there wasn't much interest. He suspects the decision to move off Solid had already been made by then. A few bug reports he managed to surface did make it into fixes now live in the Solid 2.0 beta branch — feedback he thinks could have mattered a lot more if it had come earlier. He pushed back specifically on the idea that this says anything meaningful about signals as an architecture at scale. Fine-grained reactive systems power serious infrastructure elsewhere — he points to Bloomberg, where similar signal-based reactivity underlies stock market prediction systems (different language, same underlying idea). His read: agents are trained heavily on React because React has been dominant, and that dominance is partly what's keeping it dominant. He compares it to what happened with Builder's Mitosis — trading a tighter model for a looser, more agent-friendly one. Whether that's the right direction long-term, he's not sure. Neither am I, honestly. It's one of those calls where the practical reason (agents are better at it) and the technical reason (is this actually better?) are pulling in opposite directions. Meanwhile, Solid 2.0 RC is out and worth trying. StackBlitz has CSR and SSR starter templates up if you want to poke at it without any local setup. Carniato's also been writing a three-part deep dive on Solid's async model, arguing it's genuinely different from how other frameworks handle it — not just Suspense with a new name. A few other things worth knowing about from the same week: - Lovable moved its stack from Next.js to TanStack Start. - Someone dug into the shadow economy of LLM token brokers reselling discounted API tokens. - A neat CSS paint-order trick made the rounds, along with a writeup on a CSS-based email exploit. - Expo published best practices for React Native OTA updates. - pnpm 12 RC is now rewritten in Rust. - A new syntax highlighter is using the CSS Custom Highlights API instead of the usual tokenizer-plus-spans approach. - Convex raised a $57M Series B. - Yelp wrote about migrating its Flow codebase to TypeScript across a large monorepo. - Vitest 5 changed clearMocks to be on by default — worth checking your test suite if you upgrade. - Shopify shared a context-compression technique for LLMs they're calling "gisting." ## Questions this post answers ### What's new in Solid 2.0 release candidate? Solid 2.0 RC makes async first-class in the reactive core: computations can return promises directly and the dependency graph automatically suspends and resumes around them, removing the need to manually wire loading states or use extra libraries for fetches inside reactive computations. The release also adds optimistic mutations and a reactive core rebuilt from scratch rather than patched onto the previous implementation. _Frontend developers tracking SolidJS's async reactivity shift can follow the rollout on daily.dev._ ### Does SolidJS support optimistic UI updates natively? Yes, Solid 2.0 release candidate adds optimistic mutations as a built-in feature, allowing UI updates to render before a server response actually returns. This pairs with the new async-aware reactive core, which handles promises returned from computations without requiring separate state management for loading or pending states. _Anyone weighing state management approaches for async UI can watch this pattern evolve via daily.dev._ ## Community take How the wider developer community reacted, aggregated from 2 discussions across x (as of 2026-08-19). **TL;DR:** No substantive discussion content was provided, so community sentiment cannot be assessed. **Sentiment:** 34% positive · 33% mixed · 33% skeptical **By community** - x (mixed): No usable comment content was available to determine a lean. **Source threads** - [x](https://x.com/solid_js/status/2090129688731820173) · 0 points · 0 comments - [x](https://x.com/RyanCarniato/status/2090163510164762930) · 0 points · 0 comments --- Tags: [#javascript](https://daily.dev/tags/javascript), [#solidjs](https://daily.dev/tags/solidjs) [View this post on daily.dev](https://daily.dev/posts/solid-2-0-hits-release-candidate-with-first-class-async-support-fwnxbelqc) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Solid 2.0 hits Release Candidate with first-class async support","url":"https://daily.dev/posts/solid-2-0-hits-release-candidate-with-first-class-async-support-fwnxbelqc","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/solid-2-0-hits-release-candidate-with-first-class-async-support-fwnxbelqc"},"datePublished":"2026-08-13T18:09:37.700Z","dateModified":"2026-08-19T22:08:26.781Z","description":"Solid 2.0 has reached Release Candidate status with async support built directly into its reactive core. Computations can now return promises directly, letting...","isAccessibleForFree":true,"articleSection":"Collections","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Collections","logo":"https://media.daily.dev/image/upload/s--fk_6ycEi--/f_auto,q_auto/v1780996001/logos/collections?_a=BAMAMiWQ0","url":"https://daily.dev/sources/collections"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/solid-2-0-hits-release-candidate-with-first-class-async-support-fwnxbelqc","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":1},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"javascript,solidjs","timeRequired":"PT3M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Collections","item":"https://daily.dev/sources/collections"},{"@type":"ListItem","position":3,"name":"Solid 2.0 hits Release Candidate with first-class async support"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/solid-2-0-hits-release-candidate-with-first-class-async-support-fwnxbelqc#faq","mainEntity":[{"@type":"Question","name":"What's new in Solid 2.0 release candidate?","acceptedAnswer":{"@type":"Answer","text":"Solid 2.0 RC makes async first-class in the reactive core: computations can return promises directly and the dependency graph automatically suspends and resumes around them, removing the need to manually wire loading states or use extra libraries for fetches inside reactive computations. The release also adds optimistic mutations and a reactive core rebuilt from scratch rather than patched onto the previous implementation. Frontend developers tracking SolidJS's async reactivity shift can follow the rollout on daily.dev."}},{"@type":"Question","name":"Does SolidJS support optimistic UI updates natively?","acceptedAnswer":{"@type":"Answer","text":"Yes, Solid 2.0 release candidate adds optimistic mutations as a built-in feature, allowing UI updates to render before a server response actually returns. This pairs with the new async-aware reactive core, which handles promises returned from computations without requiring separate state management for loading or pending states. Anyone weighing state management approaches for async UI can watch this pattern evolve via daily.dev."}}]} ```