Repository navigation
Conversation
…tats - Why Solid rows follow the website highlights list: components run once, async is just a value, transitions without a transition API (replaces the split-effects row), optimistic UI you already wrote, and a new server functions row (use server, live, broadcast). - About: drop split effects from the pioneered card; Solid 1.0 dated 28 Jun 2021, add the 2.0 beta (3 Mar 2026), date 2.0 stable 16 Nov 2026. Release dates are from the solidjs/solid GitHub releases. - Stats fallbacks: GitHub stars and contributors as of 2026-11-16; npm downloads stay null. Remove the unused STATS_FALLBACK copy in site.ts. - French catalog updated for every changed or new string. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0117BoWLb4JQcLEieBURa2cZ
🚀 Deploying Preview to Cloudflare 🚀Preview Deployments by commit
|
Split effects are a change from 1.x, not a feature to sell, so the "Split effects" tab is gone. The four live examples now follow the v2 tutorials: - Async: tabbed pages from an async memo, with isPending dimming the current page and latest() marking the tab you just clicked. - Draft stores: a cart edited through drafts (push, splice, nested increments) with a derived total. - Projections (new): a thousand-row selection where a click re-runs two rows, with the count shown on screen. - Optimistic actions: a todo list with add and toggle actions, pending styling, and a "Fail the next save" switch that shows the guess discarding itself and the error surfacing. Each example type-checks against solid-js and @solidjs/web 2.0.0-rc.22 and was run in Chromium. French strings updated. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0117BoWLb4JQcLEieBURa2cZ
Cuts filler and stock phrasing: "a reactive core you can reason about", "by people like you", "steward", "removes whole classes of problems", "the industry took notice", "Others followed.", "giving the growing community a home", "as the project heads toward 2.0", "precise, modern sans-serif ... carries the brand", "compact and confident", "Here is how the two are used", "Try each one live, right here", "Every profit". Facts are unchanged. Supporter bios carried over from the old site are left as written, apart from a typo fix. French catalog rekeyed. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0117BoWLb4JQcLEieBURa2cZ
…leanly Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0117BoWLb4JQcLEieBURa2cZ
Solid does not use the term. The Why Solid row becomes "Consistent updates", and the section and pioneered-card copy no longer mention it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0117BoWLb4JQcLEieBURa2cZ
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0117BoWLb4JQcLEieBURa2cZ
brenelz
approved these changes
Nov 16, 2026
Follows the v2 tutorial: two async memos where one depends on the other, isPending disabling the city select, and a writable derived signal that resets the city with no effect. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0117BoWLb4JQcLEieBURa2cZ
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Requested by Ryan · project thread
Content pass on the
solid-2-sitebranch, on top of #598 (brenelz's review fixes). It does not touch any line #598 changes, and a local merge of both is clean. Once both merge, split effects are no longer pitched anywhere on the site except the historical RC blog post.What changed
Home, "What's new in Solid 2.0" (the live REPL tabs): split effects are a change from 1.x, not a feature to sell, so that tab is gone. The examples are rewritten following the v2 tutorials (solid-docs
src/tutorials):isPendingdisables the city select while it reloads, and a writable derived signal resets the city with no effect. The<Loading>fallback shows on the first load only.push,splice) with a derived total.Home, "Why Solid 2.0?": the rows now follow Ryan's website highlights list.
isPending,latest) replaces the split-effects row. The site does not use the term "transitions"."use server",live(),broadcast()).Copy pass across the site removes phrasing that reads as AI-written:
The facts are unchanged. Supporter bios carried over from the old site are left as their authors wrote them, apart from a typo fix.
About
Stats fallbacks: GitHub stars 36,273 and contributors 198 as of 2026-11-16. npm downloads stay
null. Also removed the unused duplicateSTATS_FALLBACKfromsite.ts.French: every changed or new string is in
fr.ts. One stale entry ("Others followed. …") is kept on purpose, because removing it would conflict with #598's neighbouring line. It can go once both merge.Checked
strictagainst solid-js and @solidjs/web 2.0.0-rc.22.pnpm buildpasses, andtscshows the same 6 errors as the base branch and no new ones.CI note
The "Workers Builds: solid2-site" check also fails on the base branch head (a43d509) and on #598, so it is not caused by this PR. Its log is only on the Cloudflare dashboard.
Still needs a person (not done here)
/media.https://claude.ai/code/session_0117BoWLb4JQcLEieBURa2cZ
Generated by Claude Code