Use `@solidjs/diagnostics` to capture evidence from Solid 2.0 scenarios. Check diagnostic findings, rerun and waste budgets, the visible response to user interactions, and server-render waits and calls, then compare captures after repairs.
- Checking generated or ported Solid code
- Setting rerun and wasted-work limits
- Finding why a scope reruns
solidjs/solid☆ 36.4KUpdated Nov 17, 2026
Use this primer when writing, reviewing, or migrating Solid 2.0 code. It explains core API patterns, highlights differences from Solid 1.x and React, and shows the appropriate primitives for reactive values, effects, stores, async work, and UI boundaries.
- Writing a new Solid 2.0 component
- Reviewing unfamiliar Solid 2.0 code
- Migrating a Solid 1.x project
solidjs/solid☆ 36.4KUpdated Nov 17, 2026
Use this guide to interpret Solid 2.0 diagnostic codes from warnings, test failures, or captured reports. It explains what each finding means and gives concrete repairs for tracking, writes, ownership, loading boundaries, and performance issues.
- Fixing a Solid warning or test failure
- Tracing a diagnostic code to its cause
- Reducing unnecessary reactive work
solidjs/solid☆ 36.4KUpdated Nov 17, 2026
Use this guide to write or review Solid 2.0 server components that return templates. It explains where server markup belongs, how client components fill slots, and how to handle forms, event behavior, shared components, and compilation setup.
- Writing a Solid server component
- Deciding whether markup belongs on server or client
- Passing client behavior through a slot
solidjs/solid☆ 36.4KUpdated Nov 17, 2026