experimental: Solid 2.0 migration powered by AI by davedbase · Pull Request #1437 · solidjs/solid-docs

davedbase · 2026-03-04T03:21:58Z

This is an implementation of the docs generated from RFCs for Solid 2.0. Claude was prompted to use the PLAN.md and a cloned copy of the RFCs in the new-docs folder. It was tasked to outline what the 2.0 docs would look like. Note that this is an experiment to evaluate how close it got with little effort or guidance. This PR will either be deleted or evolved into additional docs for the 2.0 beta release.

bolt-new-by-stackblitz · 2026-03-04T03:22:00Z

Run & review this pull request in StackBlitz Codeflow.

netlify · 2026-03-04T03:22:03Z

✅ Deploy Preview for solid-docs ready!

Name	Link
🔨 Latest commit	`57120cd`
🔍 Latest deploy log	https://app.netlify.com/projects/solid-docs/deploys/69a7ac0b8f179d0008b090ad
😎 Deploy Preview	https://deploy-preview-1437--solid-docs.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

devagrawal09 · 2026-03-04T09:05:52Z

src/routes/advanced-concepts/async-reactivity.mdx

+## Mutations: `action` + `refresh`
+
+Reading async data is handled by computations and boundaries.
+**Writing** data — mutations — uses a different tool: [`action()`](/reference/reactive-utilities/action).
+
+An action wraps a generator function that can perform optimistic writes, async work, and refresh coordination in a structured way:
+
+```ts
+import { action, refresh } from "solid-js"
+import { createStore } from "solid-js/store"
+
+const [todos] = createStore(() => api.getTodos(), { list: [] })
+
+const addTodo = action(function* (todo) {
+  yield api.addTodo(todo)   // async work
+  refresh(todos)             // re-fetch the source data
+})
+```
+
+Actions run inside a transition. When the action completes and `refresh()` fires, the derived data recomputes and the UI updates.
+See the [Fetching Data](/guides/fetching-data) guide for the full mutation and optimistic update patterns.


actions are only needed to tie optimistic updates with async updates/refresh. This section should be combined with Optimistic updates below - no need to use actions if you are not setting optimistic data inside them.

devagrawal09 · 2026-03-04T09:06:56Z

src/routes/advanced-concepts/async-reactivity.mdx

+## Optimistic updates
+
+For instant UI feedback during mutations, Solid 2.0 provides two optimistic primitives:
+
+- [`createOptimistic`](/reference/reactive-utilities/create-optimistic) — a signal whose writes revert when the transition completes
+- [`createOptimisticStore`](/reference/reactive-utilities/create-optimistic-store) — the store equivalent
+
+Optimistic values overlay on top of a source during a transition and automatically roll back when the transition settles (on both success and failure):


Replace transition with action, and in general i think we want to avoid talking about transitions if possible

devagrawal09 · 2026-03-04T09:08:11Z

src/routes/advanced-concepts/async-reactivity.mdx

+const [todos] = createStore(() => api.getTodos(), { list: [] })
+const [optimisticTodos, setOptimisticTodos] = createOptimisticStore(
+  () => snapshot(todos),
+  { list: [] }
+)


Suggested change

const [todos] = createStore(() => api.getTodos(), { list: [] })

const [optimisticTodos, setOptimisticTodos] = createOptimisticStore(

() => snapshot(todos),

{ list: [] }

)

const [todos, setOptimisticTodos] = createOptimisticStore(

() => api.getTodos(),

{ list: [] }

)

devagrawal09 · 2026-03-04T09:09:57Z

src/routes/advanced-concepts/async-reactivity.mdx

+## Error handling
+
+Errors in async computations are caught by [`<Errored>`](/reference/components/error-boundary) boundaries, just like synchronous errors:
+
+```tsx
+<Errored fallback={(err) => <p>Something went wrong: {err.message}</p>}>
+  <Loading fallback={<Spinner />}>
+    <UserProfile />
+  </Loading>
+</Errored>
+```
+
+If a fetch rejects or a computation throws, the nearest `<Errored>` boundary renders its fallback.


Might be worth adding an example with the retry method as well

devagrawal09 · 2026-03-04T09:34:44Z

src/routes/concepts/control-flow/list-rendering.mdx

+## When to use `<For>` vs `<Repeat>`
+
+- Use `<For>` when rendering from a **data array** where items have identity and may change, reorder, or be filtered.
+- Use `<Repeat>` when rendering a **fixed count** of items (skeletons, ranges, grids) where no list diffing is needed.


Not sure the point about Repeat is accurate - it's not for fixed count of items, but for arrays where things don't move around much (chats, logs, etc). Probably gonna need some workshopping.

devagrawal09 · 2026-03-04T09:58:33Z

src/routes/guides/complex-state-management.mdx

 			<For each={tasks()}>
 				{(task) => {
-					const { id, text } = task
+					const { id, text } = task()


reading a signal top level bad

devagrawal09 · 2026-03-04T10:02:03Z

src/routes/reference/components/error-boundary.mdx


 - `err`: The caught error object.
- `reset`: A function that forces the `<ErrorBoundary>` to re-render its children and clear the error state.
+- `reset`: A function that forces `<Errored>` to re-render its children and clear the error state.


reset doesn't force rerender of the children, it forces a rerun of the errored computations and nothing else

devagrawal09 · 2026-03-04T10:03:26Z

src/routes/reference/components/repeat.mdx

+function Repeat(props: {
+  count: number
+  from?: number
+  children: (index: () => number) => JSX.Element


Suggested change

children: (index: () => number) => JSX.Element

children: (index: number) => JSX.Element

Index isn't an accessor since it can't change

devagrawal09 · 2026-03-04T10:03:55Z

src/routes/reference/components/repeat.mdx

+Use `<Repeat>` when:
+- You need to render a fixed number of elements (e.g., star ratings, pagination dots, grid cells)
+- The content doesn't come from a data array
+- You don't need list diffing or keying
+
+Use `<For>` when:
+- You're rendering items from a data array
+- Items have identity and may be reordered, added, or removed


Definitely gonna need more workshopping

devagrawal09 · 2026-03-04T10:07:27Z

src/routes/reference/lifecycle/on-settled.mdx

+description: >-
+  Run code after component rendering is complete with onSettled. Replaces
+  onMount with added cleanup support and clearer semantics.
+---
+
+```ts
+import { onSettled } from "solid-js"
+
+function onSettled(fn: () => void | (() => void)): void
+```
+
+`onSettled` registers a callback that runs once after the component's initial render is complete and the DOM is ready. It replaces `onMount` from Solid 1.x.
+
+## Key differences from `onMount`
+
+- **Can return a cleanup function** — the returned function runs when the component is disposed
+- **Cannot create nested reactive primitives** — don't call `createSignal`, `createEffect`, etc. inside the callback
+


Also gonna need workshopping
The key change is the onSettled can be called from event handlers as well, where it will queue the callback to run after any updates made in the event are settled/flushed

davedbase and others added 14 commits October 27, 2025 18:18

Added use case and tags generated by Claude

1c43f58

Added Solid standard banner to README ;)

f6c6dc0

Merge branch 'main' into main

08a0ffe

Added descriptions and adjusted use cases/tags

45450a5

Merge branch 'main' of https://github.com/davedbase/solid-docs

cbc027b

Removed security note

fe3539d

Merge remote-tracking branch 'upstream/main'

90f6787

Added plan

0937464

Generated changes for Phase 1

f4104dc

Generated phase 2

68ca59f

Generated phase 3

127cf4d

Geneated phase 4

7a9bdf7

Generated phase 5

adbf8e8

Added additional sections

afd855c

davedbase added 3 commits March 3, 2026 22:35

Asked Claude to review and correct anything it thought needed adjustment

35ffaf6

Removed new-docs subproject from tripping up Netlify deploy

e5e256c

Adjusted stores and added more detail on projections

57120cd

devagrawal09 requested changes Mar 4, 2026

View reviewed changes

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

experimental: Solid 2.0 migration powered by AI#1437

experimental: Solid 2.0 migration powered by AI#1437
davedbase wants to merge 17 commits intosolidjs:mainfrom
davedbase:solid2-docs

davedbase commented Mar 4, 2026

Uh oh!

bolt-new-by-stackblitz bot commented Mar 4, 2026

Uh oh!

netlify bot commented Mar 4, 2026 •

edited

Loading

Uh oh!

devagrawal09 Mar 4, 2026

Uh oh!

devagrawal09 Mar 4, 2026

Uh oh!

devagrawal09 Mar 4, 2026

Uh oh!

devagrawal09 Mar 4, 2026

Uh oh!

devagrawal09 Mar 4, 2026

Uh oh!

devagrawal09 Mar 4, 2026

Uh oh!

devagrawal09 Mar 4, 2026

Uh oh!

devagrawal09 Mar 4, 2026

Uh oh!

devagrawal09 Mar 4, 2026

Uh oh!

devagrawal09 Mar 4, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

	children: (index: () => number) => JSX.Element
	children: (index: number) => JSX.Element

Conversation

davedbase commented Mar 4, 2026

Uh oh!

bolt-new-by-stackblitz bot commented Mar 4, 2026

Uh oh!

netlify bot commented Mar 4, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

✅ Deploy Preview for solid-docs ready!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

netlify bot commented Mar 4, 2026 •

edited

Loading