solidjs-state

createSignal manages primitive SolidJS state values, while createStore handles nested objects and arrays with fine-grained reactivity. Choose signals for local independent data and stores for structured cross-cutting state requiring targeted property updates.

The best way to avoid prop drilling in SolidJS is by using Context. Create a Context Provider to share state globally across the component tree, and access it via custom useX hooks to cleanly retrieve data without passing props manually.

Use createResource or createAsync for SolidJS data fetching when loading server data asynchronously. These primitives handle remote interactions and server data fetching in SolidStart and SolidRouter, managing loading states and memoized updates predictably.

Safely update nested SolidJS stores by applying produce for immutable-style mutable drafts or reconcile to diff and sync server data. These methods ensure predictable UI data handling and prevent unnecessary re-renders during complex state mutations.

SolidJS Context works well for sharing cross-cutting state globally, but for server data fetching, combining Context with createResource is recommended. This pattern safely lifts state and manages async server interactions without prop drilling.