SolidJS for React Developers
summary
Solid claims: SolidJS uses createSignal getters, components run once (not re-rendered) and the compiler tracks DOM dependencies so there’s no virtual DOM and updates mutate only affected nodes. Expect concrete APIs: createEffect, createMemo, createStore, onMount/onCleanup, classList, batch and directives; a worked example connects an existing form library via a low‑level prop and it behaves correctly. Watch for practical pitfalls: don’t read signal values before JSX and don’t destructure props.
AI-written summary · about
chapters (23)
- 0:00SolidJS for React devs
- 1:11Imperative vs declarative vs reactive
- 4:28Signals in SolidJS
- 7:17React vs SolidJS syntax
- 8:22Counter example React vs SolidJS
- 9:48Automatic counter with useEffect
- 10:30SolidJS lifecycle
- 11:53SolidJS beginner mistakes
- 13:41Props in SolidJS
- 14:23useEffect vs createEffect
- 16:12useMemo vs derived signals
- 17:19Flow control in SolidJS
- 19:04Looping React vs SolidJS
- 19:46Error boundaries in SolidJS
- 20:30Styling React vs SolidJS
- 20:50Class management in SolidJS
- 22:15Lifecycle methods in SolidJS
- 23:19SolidJS API similarities
- 24:03Stores and batching in SolidJS
- 24:47Directives and advanced features
- 25:29SolidJS pitfalls recap
- 26:13Performance React vs SolidJS
- 27:41React vs SolidJS choice
