@solidjs/signals 0.13.13 → 2.0.0-beta.10

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (55) hide show
  1. package/README.md +8 -7
  2. package/dist/dev.js +502 -244
  3. package/dist/node.cjs +1501 -1308
  4. package/dist/prod.js +1134 -929
  5. package/dist/types/boundaries.d.ts +124 -3
  6. package/dist/types/core/action.d.ts +34 -0
  7. package/dist/types/core/constants.d.ts +24 -0
  8. package/dist/types/core/context.d.ts +10 -2
  9. package/dist/types/core/core.d.ts +108 -9
  10. package/dist/types/core/dev.d.ts +1 -1
  11. package/dist/types/core/effect.d.ts +3 -2
  12. package/dist/types/core/error.d.ts +24 -0
  13. package/dist/types/core/external.d.ts +19 -0
  14. package/dist/types/core/graph.d.ts +1 -0
  15. package/dist/types/core/owner.d.ts +93 -3
  16. package/dist/types/core/scheduler.d.ts +27 -2
  17. package/dist/types/core/types.d.ts +3 -6
  18. package/dist/types/index.d.ts +2 -2
  19. package/dist/types/map.d.ts +32 -3
  20. package/dist/types/signals.d.ts +338 -39
  21. package/dist/types/store/optimistic.d.ts +38 -12
  22. package/dist/types/store/projection.d.ts +55 -15
  23. package/dist/types/store/reconcile.d.ts +22 -0
  24. package/dist/types/store/store.d.ts +72 -15
  25. package/dist/types/store/storePath.d.ts +28 -0
  26. package/dist/types/store/utils.d.ts +78 -7
  27. package/dist/types-cjs/boundaries.d.cts +173 -0
  28. package/dist/types-cjs/core/action.d.cts +35 -0
  29. package/dist/types-cjs/core/async.d.cts +6 -0
  30. package/dist/types-cjs/core/constants.d.cts +49 -0
  31. package/dist/types-cjs/core/context.d.cts +36 -0
  32. package/dist/types-cjs/core/core.d.cts +153 -0
  33. package/dist/types-cjs/core/dev.d.cts +49 -0
  34. package/dist/types-cjs/core/effect.d.cts +31 -0
  35. package/dist/types-cjs/core/error.d.cts +38 -0
  36. package/dist/types-cjs/core/external.d.cts +45 -0
  37. package/dist/types-cjs/core/graph.d.cts +4 -0
  38. package/dist/types-cjs/core/heap.d.cts +14 -0
  39. package/dist/types-cjs/core/index.d.cts +12 -0
  40. package/dist/types-cjs/core/lanes.d.cts +54 -0
  41. package/dist/types-cjs/core/owner.d.cts +116 -0
  42. package/dist/types-cjs/core/scheduler.d.cts +106 -0
  43. package/dist/types-cjs/core/types.d.cts +83 -0
  44. package/dist/types-cjs/index.d.cts +9 -0
  45. package/dist/types-cjs/map.d.cts +53 -0
  46. package/dist/types-cjs/package.json +3 -0
  47. package/dist/types-cjs/signals.d.cts +491 -0
  48. package/dist/types-cjs/store/index.d.cts +9 -0
  49. package/dist/types-cjs/store/optimistic.d.cts +45 -0
  50. package/dist/types-cjs/store/projection.d.cts +66 -0
  51. package/dist/types-cjs/store/reconcile.d.cts +23 -0
  52. package/dist/types-cjs/store/store.d.cts +125 -0
  53. package/dist/types-cjs/store/storePath.d.cts +58 -0
  54. package/dist/types-cjs/store/utils.d.cts +114 -0
  55. package/package.json +32 -24
@@ -0,0 +1,491 @@
1
+ import type { Disposable } from "./core/index.cjs";
2
+ /**
3
+ * Low-level reactive-cleanup primitive. Registers a callback that runs when
4
+ * the surrounding owner is disposed.
5
+ *
6
+ * **In 2.0 user code this is rare.** The two cases where you might reach for
7
+ * it have better-shaped tools:
8
+ *
9
+ * - **Component lifecycle (mount/unmount, listeners, intervals):** use
10
+ * {@link onSettled} and **return** a cleanup function. Setup and teardown
11
+ * stay paired in one block. This replaces the 1.x `onMount` + `onCleanup`
12
+ * pairing.
13
+ * - **Cleanup tied to an effect run:** `onCleanup` does not belong in
14
+ * `createEffect`'s apply phase. If a compute phase genuinely needs per-run
15
+ * teardown, that's usually a sign the work should be a memo/projection
16
+ * instead, or moved to `onSettled` if it's lifecycle-shaped.
17
+ *
18
+ * Where `onCleanup` is the right tool is **library / custom-primitive
19
+ * internals** — coordinating disposal inside a `createRoot` body, or wiring
20
+ * cleanup to a captured owner via `runWithOwner` from a custom factory.
21
+ * Application code rarely needs to write any of those shapes directly.
22
+ *
23
+ * Must be called inside an owner. Calling outside an owner is a no-op (with a
24
+ * dev-mode warning).
25
+ *
26
+ * Cannot be used inside `createTrackedEffect` or `onSettled` — return a
27
+ * cleanup function from the callback body instead.
28
+ *
29
+ * @example
30
+ * ```ts
31
+ * // Library shape: thread a resource's disposal into a *captured* owner
32
+ * // from a factory that has no settle-phase setup of its own. `onSettled`
33
+ * // would queue a callback we don't need; `onCleanup` is the leaner
34
+ * // primitive when the only job is "register disposal on this owner".
35
+ * function bindToOwner<T extends { dispose(): void }>(owner: Owner, resource: T): T {
36
+ * runWithOwner(owner, () => onCleanup(() => resource.dispose()));
37
+ * return resource;
38
+ * }
39
+ * ```
40
+ */
41
+ export declare function onCleanup(fn: Disposable): Disposable;
42
+ /**
43
+ * A zero-arg getter for a reactive value. Calling it inside a tracking scope
44
+ * (memo, effect compute, JSX expression) subscribes the scope to changes.
45
+ *
46
+ * Reading outside any tracking scope simply returns the current value without
47
+ * creating a subscription.
48
+ */
49
+ export type Accessor<T> = () => T;
50
+ export declare function accessor<T>(node: any): Accessor<T>;
51
+ /**
52
+ * A signal setter. Accepts either a new value or an updater `(prev) => next`.
53
+ *
54
+ * If the type permits `undefined`, `setState()` (no args) clears to `undefined`.
55
+ *
56
+ * To store a function as the value itself (rather than as an updater), wrap it
57
+ * with an updater: `setHandler(() => myHandler)`.
58
+ */
59
+ export type Setter<in out T> = {
60
+ <U extends T>(...args: undefined extends T ? [] : [value: Exclude<U, Function> | ((prev: T) => U)]): undefined extends T ? undefined : U;
61
+ <U extends T>(value: (prev: T) => U): U;
62
+ <U extends T>(value: Exclude<U, Function>): U;
63
+ <U extends T>(value: Exclude<U, Function> | ((prev: T) => U)): U;
64
+ };
65
+ /** A `[get, set]` pair returned from `createSignal` / `createOptimistic`. */
66
+ export type Signal<T> = [get: Accessor<T>, set: Setter<T>];
67
+ export type ComputeFunction<Prev, Next extends Prev = Prev> = (v: Prev) => PromiseLike<Next> | AsyncIterable<Next> | Next;
68
+ export type EffectFunction<Prev, Next extends Prev = Prev> = (v: Next, p?: Prev) => (() => void) | void;
69
+ export type EffectBundle<Prev, Next extends Prev = Prev> = {
70
+ effect: EffectFunction<Prev, Next>;
71
+ error: (err: unknown, cleanup: () => void) => void;
72
+ };
73
+ /** Options shared by every effect primitive. */
74
+ interface BaseEffectOptions {
75
+ /** Debug name (dev mode only) */
76
+ name?: string;
77
+ }
78
+ /** Options for effect primitives that support deferring/scheduling their initial run (`createEffect`, `createRenderEffect`, `createReaction`). */
79
+ export interface EffectOptions extends BaseEffectOptions {
80
+ /** When true, defers the initial effect execution until the next change */
81
+ defer?: boolean;
82
+ /**
83
+ * When true, enqueues the initial effect callback through the effect queue instead of running
84
+ * it synchronously at creation. Lets the initial run participate in transitions -- if any
85
+ * source throws `NotReadyError` during the compute phase, the callback is held until the
86
+ * transition settles.
87
+ *
88
+ * Primarily for render effects that need transition-aware initial mounts (e.g. the root
89
+ * `insert()` in `render()`).
90
+ */
91
+ schedule?: boolean;
92
+ }
93
+ /** Options for plain signals created with `createSignal(value)` or `createOptimistic(value)`. */
94
+ export interface SignalOptions<T> {
95
+ /** Debug name (dev mode only) */
96
+ name?: string;
97
+ /**
98
+ * Custom equality function, or `false` to always notify subscribers.
99
+ * Defaults to reference equality (`isEqual`). Pass a comparator (e.g.
100
+ * `(a, b) => a.id === b.id`) for value-based equality, or `false` to
101
+ * notify on every write regardless of equality.
102
+ */
103
+ equals?: false | ((prev: T, next: T) => boolean);
104
+ /** Suppress dev-mode warnings when writing inside an owned scope */
105
+ ownedWrite?: boolean;
106
+ /** Callback invoked when the signal loses all subscribers */
107
+ unobserved?: () => void;
108
+ }
109
+ /**
110
+ * Options for read-only memos created with `createMemo`.
111
+ * Also used in combination with `SignalOptions` for writable memos
112
+ * (`createSignal(fn)` / `createOptimistic(fn)`).
113
+ */
114
+ export interface MemoOptions<T> {
115
+ /** Stable identifier for the owner hierarchy */
116
+ id?: string;
117
+ /** Debug name (dev mode only) */
118
+ name?: string;
119
+ /** When true, the owner is invisible to the ID scheme -- inherits parent ID and doesn't consume a childCount slot */
120
+ transparent?: boolean;
121
+ /**
122
+ * Custom equality function, or `false` to always notify subscribers.
123
+ * Defaults to reference equality (`isEqual`). Pass a comparator (e.g.
124
+ * `(a, b) => a.id === b.id`) for value-based equality, or `false` to
125
+ * notify on every recompute regardless of equality.
126
+ */
127
+ equals?: false | ((prev: T, next: T) => boolean);
128
+ /** Callback invoked when the computed loses all subscribers */
129
+ unobserved?: () => void;
130
+ /**
131
+ * When true, defers the initial computation until the value is first read,
132
+ * **and** opts the memo into autodisposal — once it has no remaining
133
+ * subscribers it is torn down and recomputed from scratch on the next read.
134
+ * Use it for compute-on-demand values that should not retain state across
135
+ * idle periods. Non-lazy owned memos live for their owner's lifetime and
136
+ * never autodispose.
137
+ */
138
+ lazy?: boolean;
139
+ }
140
+ export type NoInfer<T extends any> = [T][T extends any ? 0 : never];
141
+ /**
142
+ * Creates a simple reactive state with a getter and setter.
143
+ *
144
+ * When called with a plain value, creates a signal with `SignalOptions` (name, equals, ownedWrite, unobserved).
145
+ * When called with a function, creates a writable memo with `SignalOptions & MemoOptions` (adds id, lazy).
146
+ *
147
+ * ```typescript
148
+ * // Plain signal
149
+ * const [state, setState] = createSignal<T>(value, options?: SignalOptions<T>);
150
+ * // Writable memo (function overload)
151
+ * const [state, setState] = createSignal<T>(fn, initialValue?, options?: SignalOptions<T> & MemoOptions<T>);
152
+ * ```
153
+ * @param value initial value of the state; if empty, the state's type will automatically extended with undefined
154
+ * @param options optional object with a name for debugging purposes and equals, a comparator function for the previous and next value to allow fine-grained control over the reactivity
155
+ *
156
+ * @returns `[state: Accessor<T>, setState: Setter<T>]`
157
+ *
158
+ * @example
159
+ * ```ts
160
+ * const [count, setCount] = createSignal(0);
161
+ *
162
+ * count(); // 0
163
+ * setCount(1); // explicit value
164
+ * setCount(c => c + 1); // updater
165
+ * ```
166
+ *
167
+ * @example
168
+ * ```ts
169
+ * // Writable memo: starts as `fn()`, can be locally overwritten by setter.
170
+ * const [user, setUser] = createSignal(() => fetchUser(userId()));
171
+ *
172
+ * setUser({ ...user(), name: "Alice" }); // optimistic local edit
173
+ * ```
174
+ *
175
+ * @description https://docs.solidjs.com/reference/basic-reactivity/create-signal
176
+ */
177
+ export declare function createSignal<T>(): Signal<T | undefined>;
178
+ export declare function createSignal<T>(value: Exclude<T, Function>, options?: SignalOptions<T>): Signal<T>;
179
+ export declare function createSignal<T>(fn: ComputeFunction<T>, options?: SignalOptions<T> & MemoOptions<T>): Signal<T>;
180
+ /**
181
+ * Creates a readonly derived reactive memoized signal.
182
+ *
183
+ * ```typescript
184
+ * const value = createMemo<T>(compute, options?: MemoOptions<T>);
185
+ * ```
186
+ * @param compute a function that receives its previous value and returns a new value used to react on a computation
187
+ * @param options `MemoOptions` -- id, name, equals, unobserved, lazy
188
+ *
189
+ * @example
190
+ * ```ts
191
+ * const [first, setFirst] = createSignal("Ada");
192
+ * const [last, setLast] = createSignal("Lovelace");
193
+ *
194
+ * const fullName = createMemo(() => `${first()} ${last()}`);
195
+ *
196
+ * fullName(); // "Ada Lovelace"
197
+ * ```
198
+ *
199
+ * @example
200
+ * ```ts
201
+ * // Async memo — reads surface as pending inside <Loading>
202
+ * const user = createMemo(async () => {
203
+ * const res = await fetch(`/users/${id()}`);
204
+ * return res.json();
205
+ * });
206
+ * ```
207
+ *
208
+ * @description https://docs.solidjs.com/reference/basic-reactivity/create-memo
209
+ */
210
+ export declare function createMemo<T>(compute: ComputeFunction<undefined | NoInfer<T>, T>, options?: MemoOptions<T>): Accessor<T>;
211
+ /**
212
+ * Creates a reactive effect with **separate compute and effect phases**.
213
+ *
214
+ * - `compute(prev)` runs reactively — *put all reactive reads here*. The
215
+ * returned value is passed to `effect` and is also the new "previous" value
216
+ * for the next run.
217
+ * - `effect(next, prev?)` runs imperatively (untracked) after the queue
218
+ * flushes. *Put DOM writes / fetch / logging / subscriptions here.* It may
219
+ * return a cleanup function which runs before the next effect or on
220
+ * disposal.
221
+ *
222
+ * Reactive reads inside `effect` will *not* re-trigger this effect — that's
223
+ * intentional. If you need a single-phase tracked effect, use
224
+ * `createTrackedEffect` (with the tradeoffs noted there).
225
+ *
226
+ * Pass an `EffectBundle` (`{ effect, error }`) instead of a plain function to
227
+ * intercept errors thrown from the compute or effect phases.
228
+ *
229
+ * ```typescript
230
+ * createEffect<T>(compute, effectFn | { effect, error }, options?: EffectOptions);
231
+ * ```
232
+ * @param compute a function that receives its previous value and returns a new value used to react on a computation
233
+ * @param effectFn a function that receives the new value and is used to perform side effects (return a cleanup function), or an `EffectBundle` with `effect` and `error` handlers
234
+ * @param options `EffectOptions` -- name, defer, schedule
235
+ *
236
+ * @example
237
+ * ```ts
238
+ * const [count, setCount] = createSignal(0);
239
+ *
240
+ * createEffect(
241
+ * () => count(), // compute: tracks `count`
242
+ * value => console.log(value) // effect: side effect
243
+ * );
244
+ *
245
+ * setCount(1); // logs 1 after the next flush
246
+ * ```
247
+ *
248
+ * @example
249
+ * ```ts
250
+ * createEffect(
251
+ * () => userId(),
252
+ * id => {
253
+ * const ctrl = new AbortController();
254
+ * fetch(`/users/${id}`, { signal: ctrl.signal });
255
+ * return () => ctrl.abort(); // cleanup before next run / disposal
256
+ * }
257
+ * );
258
+ * ```
259
+ *
260
+ * @description https://docs.solidjs.com/reference/basic-reactivity/create-effect
261
+ */
262
+ export declare function createEffect<T>(compute: ComputeFunction<undefined | NoInfer<T>, T>, effectFn: EffectFunction<NoInfer<T>, T> | EffectBundle<NoInfer<T>, T>, options?: EffectOptions): void;
263
+ /**
264
+ * @deprecated `createEffect(compute)` (single argument) is no longer supported.
265
+ * Pass a separate effect function as the second argument:
266
+ * `createEffect(compute, effect)`. See [MISSING_EFFECT_FN].
267
+ *
268
+ * - For a side effect that reacts to changes, split the work:
269
+ * `createEffect(() => signal(), value => doWork(value))`.
270
+ * - For a derived value, use `createMemo(() => signal())`.
271
+ * - For a one-shot side effect at construction time, just call the function.
272
+ */
273
+ export declare function createEffect<T>(compute: ComputeFunction<undefined | NoInfer<T>, T>): never;
274
+ /**
275
+ * Creates a reactive computation that runs during the render phase as DOM elements
276
+ * are created and updated but not necessarily connected.
277
+ *
278
+ * Same compute / effect split as `createEffect`, but scheduled inside the render
279
+ * queue rather than after it. Reach for this only when authoring renderer
280
+ * plumbing (custom DOM bindings, JSX-generated `insert()` / `spread()` calls).
281
+ * App code should use `createEffect`.
282
+ *
283
+ * ```typescript
284
+ * createRenderEffect<T>(compute, effectFn, options?: EffectOptions);
285
+ * ```
286
+ * @param compute a function that receives its previous value and returns a new value used to react on a computation
287
+ * @param effectFn a function that receives the new value and is used to perform side effects
288
+ * @param options `EffectOptions` -- name, defer, schedule
289
+ *
290
+ * @example
291
+ * ```ts
292
+ * // Custom directive: bind an element's textContent to a reactive source.
293
+ * function bindText(el: HTMLElement, source: () => string) {
294
+ * createRenderEffect(
295
+ * () => source(),
296
+ * value => { el.textContent = value; }
297
+ * );
298
+ * }
299
+ * ```
300
+ *
301
+ * @description https://docs.solidjs.com/reference/secondary-primitives/create-render-effect
302
+ */
303
+ export declare function createRenderEffect<T>(compute: ComputeFunction<undefined | NoInfer<T>, T>, effectFn: EffectFunction<NoInfer<T>, T>, options?: EffectOptions): void;
304
+ /**
305
+ * Creates a tracked reactive effect where dependency tracking and side effects happen
306
+ * in the same scope.
307
+ *
308
+ * WARNING: Because tracking and effects happen in the same scope, this primitive
309
+ * may run multiple times for a single change or show tearing (reading inconsistent
310
+ * state). Use only when dynamic subscription patterns require same-scope tracking.
311
+ *
312
+ * ```typescript
313
+ * createTrackedEffect(compute, options?: { name?: string });
314
+ * ```
315
+ * @param compute a function that contains reactive reads to track and returns an optional cleanup function to run on disposal or before next execution
316
+ * @param options -- name
317
+ *
318
+ * @example
319
+ * ```ts
320
+ * createTrackedEffect(() => {
321
+ * const target = focusedNode();
322
+ * if (!target) return;
323
+ *
324
+ * const handler = () => log(target.value());
325
+ * target.on("change", handler);
326
+ *
327
+ * return () => target.off("change", handler);
328
+ * });
329
+ * ```
330
+ *
331
+ * @description https://docs.solidjs.com/reference/secondary-primitives/create-tracked-effect
332
+ */
333
+ export declare function createTrackedEffect(compute: () => void | (() => void), options?: BaseEffectOptions): void;
334
+ /**
335
+ * Creates a reactive computation that runs after the render phase with flexible tracking.
336
+ *
337
+ * ```typescript
338
+ * const track = createReaction(effectFn, options?: EffectOptions);
339
+ * track(() => { // reactive reads });
340
+ * ```
341
+ * @param effectFn a function (or `EffectBundle`) that is called when tracked function is invalidated
342
+ * @param options `EffectOptions` -- name, defer
343
+ *
344
+ * @example
345
+ * ```ts
346
+ * const [count, setCount] = createSignal(0);
347
+ *
348
+ * const track = createReaction(() => {
349
+ * console.log("count changed once, re-arm to listen again");
350
+ * track(() => count()); // re-arm
351
+ * });
352
+ *
353
+ * track(() => count()); // initial arm
354
+ *
355
+ * setCount(1); // logs once, reaction re-armed for next change
356
+ * ```
357
+ *
358
+ * @description https://docs.solidjs.com/reference/secondary-primitives/create-reaction
359
+ */
360
+ export declare function createReaction(effectFn: EffectFunction<undefined> | EffectBundle<undefined>, options?: EffectOptions): (tracking: () => void) => void;
361
+ /**
362
+ * Awaits a reactive expression and returns its first fully-settled value as a
363
+ * `Promise`. Pending async reads (`createMemo` returning a promise, etc.) are
364
+ * waited on; once the expression returns synchronously without `NotReadyError`
365
+ * the promise resolves with that value.
366
+ *
367
+ * Must be called *outside* a tracking scope — it doesn't subscribe, it just
368
+ * resolves the current value once.
369
+ *
370
+ * @example
371
+ * ```ts
372
+ * const user = createMemo(() => fetch(`/users/${id()}`).then(r => r.json()));
373
+ *
374
+ * // outside any reactive scope
375
+ * const initial = await resolve(() => user());
376
+ * ```
377
+ *
378
+ * @param fn a reactive expression to resolve
379
+ */
380
+ export declare function resolve<T>(fn: () => T): Promise<T>;
381
+ /**
382
+ * Creates an optimistic signal that can be used to optimistically update a value
383
+ * and then revert it back to the previous value at end of transition.
384
+ *
385
+ * When called with a plain value, creates an optimistic signal with `SignalOptions` (name, equals, ownedWrite, unobserved).
386
+ * When called with a function, creates a writable optimistic memo with `SignalOptions & MemoOptions` (adds id, lazy).
387
+ *
388
+ * ```typescript
389
+ * // Plain optimistic signal
390
+ * const [state, setState] = createOptimistic<T>(value, options?: SignalOptions<T>);
391
+ * // Writable optimistic memo (function overload)
392
+ * const [state, setState] = createOptimistic<T>(fn, options?: SignalOptions<T> & MemoOptions<T>);
393
+ * ```
394
+ * @param value initial value of the signal; if empty, the signal's type will automatically extended with undefined
395
+ * @param options optional object with a name for debugging purposes and equals, a comparator function for the previous and next value to allow fine-grained control over the reactivity
396
+ *
397
+ * @returns `[state: Accessor<T>, setState: Setter<T>]`
398
+ *
399
+ * @example
400
+ * ```ts
401
+ * const [todos, setTodos] = createOptimistic(initialTodos);
402
+ *
403
+ * const addTodo = action(function* (text: string) {
404
+ * const tempId = crypto.randomUUID();
405
+ * setTodos(t => [...t, { id: tempId, text, pending: true }]); // optimistic
406
+ * const saved = yield api.createTodo(text);
407
+ * setTodos(t => t.map(x => (x.id === tempId ? saved : x))); // reconcile
408
+ * });
409
+ * ```
410
+ *
411
+ * @description https://docs.solidjs.com/reference/basic-reactivity/create-optimistic-signal
412
+ */
413
+ export declare function createOptimistic<T>(): Signal<T | undefined>;
414
+ export declare function createOptimistic<T>(value: Exclude<T, Function>, options?: SignalOptions<T>): Signal<T>;
415
+ export declare function createOptimistic<T>(fn: ComputeFunction<T>, options?: SignalOptions<T> & MemoOptions<T>): Signal<T>;
416
+ /**
417
+ * Schedules `callback` to run **once** after the reactive graph has fully
418
+ * settled — i.e. once every pending async read inside the current owner has
419
+ * resolved and the queue has flushed. Each call registers a single fire; it
420
+ * does not create an ongoing subscription.
421
+ *
422
+ * The canonical lifecycle primitive in 2.0. Three main usages:
423
+ *
424
+ * - **Component-level setup-and-teardown** *(the most common shape)*: run
425
+ * setup after the component's first stable render and **return a cleanup
426
+ * function** to dispose it on owner disposal. This is the replacement for
427
+ * the 1.x `onMount` + `onCleanup` pairing — setup and teardown live in one
428
+ * block, and `onCleanup` is no longer the right tool for component
429
+ * bodies. (`onMount` no longer exists in 2.0.)
430
+ * - **Post-settle "ready" hook:** run once after a component's first stable
431
+ * render — analytics ping, focus, scroll-into-view, etc. No cleanup needed.
432
+ * - **Inside an event handler:** schedule work to run after the action /
433
+ * transition triggered by the event has completed.
434
+ *
435
+ * Reactive reads inside the callback are *not* tracked — to react to
436
+ * subsequent settles, register a new `onSettled` each time.
437
+ *
438
+ * `onCleanup` is **not** allowed inside the callback — return a cleanup
439
+ * function instead. The returned cleanup runs on owner disposal.
440
+ *
441
+ * @example
442
+ * ```tsx
443
+ * // Component-level setup + teardown — replaces onMount + onCleanup.
444
+ * // Subscribe to an external source on mount, unsubscribe on dispose.
445
+ * function useViewportWidth() {
446
+ * const [width, setWidth] = createSignal(window.innerWidth);
447
+ * onSettled(() => {
448
+ * const onResize = () => setWidth(window.innerWidth);
449
+ * window.addEventListener("resize", onResize);
450
+ * return () => window.removeEventListener("resize", onResize);
451
+ * });
452
+ * return width;
453
+ * }
454
+ * ```
455
+ *
456
+ * @example
457
+ * ```tsx
458
+ * // Post-settle "ready" hook — no cleanup needed.
459
+ * function Dashboard() {
460
+ * const data = createMemo(async () => fetchData());
461
+ *
462
+ * onSettled(() => {
463
+ * analytics.track("dashboard.ready");
464
+ * });
465
+ *
466
+ * return <Loading fallback={<Spinner />}><pre>{data()}</pre></Loading>;
467
+ * }
468
+ * ```
469
+ *
470
+ * @example
471
+ * ```tsx
472
+ * // Event-handler — runs after the action settles.
473
+ * function SaveButton() {
474
+ * const save = action(function* () {
475
+ * yield api.save();
476
+ * });
477
+ *
478
+ * const handleClick = () => {
479
+ * save();
480
+ * onSettled(() => toast("Saved!"));
481
+ * };
482
+ *
483
+ * return <button onClick={handleClick}>Save</button>;
484
+ * }
485
+ * ```
486
+ *
487
+ * @param callback Function to run; may return a cleanup function that fires
488
+ * on owner disposal
489
+ */
490
+ export declare function onSettled(callback: () => void | (() => void)): void;
491
+ export {};
@@ -0,0 +1,9 @@
1
+ export type { Store, StoreSetter, StoreNode, StoreOptions, ProjectionOptions, NotWrappable, SolidStore } from "./store.cjs";
2
+ export type { Merge, Omit } from "./utils.cjs";
3
+ export { isWrappable, createStore, $TRACK, $PROXY, $TARGET } from "./store.cjs";
4
+ export { createProjection } from "./projection.cjs";
5
+ export { createOptimisticStore } from "./optimistic.cjs";
6
+ export { reconcile } from "./reconcile.cjs";
7
+ export { storePath } from "./storePath.cjs";
8
+ export type { PathSetter, Part, StorePathRange, ArrayFilterFn, CustomPartial } from "./storePath.cjs";
9
+ export { snapshot, deep, merge, omit } from "./utils.cjs";
@@ -0,0 +1,45 @@
1
+ import { type Refreshable } from "../core/index.cjs";
2
+ import { type NoFn, type ProjectionOptions, type Store, type StoreSetter } from "./store.cjs";
3
+ /**
4
+ * The store equivalent of `createOptimistic`. Writes inside an `action`
5
+ * transition are tentative — they show up immediately but auto-revert (or
6
+ * reconcile to the action's resolved value) once the transition finishes.
7
+ *
8
+ * Use this for optimistic UI on collection-shaped data. For single-value
9
+ * optimistic state, prefer `createOptimistic`.
10
+ *
11
+ * - Plain form: `createOptimisticStore(initialValue)`.
12
+ * - Derived form: `createOptimisticStore(fn, seed, options?)` — a projection
13
+ * store whose authoritative value is recomputed by `fn` and whose
14
+ * optimistic overlay reverts after each transition.
15
+ *
16
+ * `options.key` defaults to `"id"`; specify it only when your data uses a
17
+ * different identity field (e.g. `{ key: "uuid" }` or `{ key: t => t.slug }`).
18
+ * Restating the default just adds noise.
19
+ *
20
+ * @example
21
+ * ```ts
22
+ * const [todos, setTodos] = createOptimisticStore<Todo[]>([]);
23
+ *
24
+ * // Mutation: optimistic add, then in-place reconcile to the saved row.
25
+ * const addTodo = action(function* (text: string) {
26
+ * const tempId = crypto.randomUUID();
27
+ * setTodos(t => { t.push({ id: tempId, text, pending: true }); });
28
+ * const saved = yield api.createTodo(text);
29
+ * setTodos(t => {
30
+ * const i = t.findIndex(x => x.id === tempId);
31
+ * if (i >= 0) t[i] = saved;
32
+ * });
33
+ * });
34
+ *
35
+ * // Return form: filter is the natural shape for removal.
36
+ * const removeTodo = action(function* (id: string) {
37
+ * setTodos(t => t.filter(x => x.id !== id));
38
+ * yield api.removeTodo(id);
39
+ * });
40
+ * ```
41
+ *
42
+ * @returns `[store: Store<T>, setStore: StoreSetter<T>]`
43
+ */
44
+ export declare function createOptimisticStore<T extends object = {}>(store: NoFn<T> | Store<NoFn<T>>): [get: Store<T>, set: StoreSetter<T>];
45
+ export declare function createOptimisticStore<T extends object = {}>(fn: (store: T) => void | T | Promise<void | T> | AsyncIterable<void | T>, store: Partial<T> | Store<NoFn<T>>, options?: ProjectionOptions): [get: Refreshable<Store<T>>, set: StoreSetter<T>];
@@ -0,0 +1,66 @@
1
+ import { type Computed, type Refreshable } from "../core/index.cjs";
2
+ import { type ProjectionOptions, type Store } from "./store.cjs";
3
+ export declare function createProjectionInternal<T extends object = {}>(fn: (draft: T) => void | T | Promise<void | T> | AsyncIterable<void | T>, seed: Partial<T>, options?: ProjectionOptions): {
4
+ store: Refreshable<Store<T>>;
5
+ node: Computed<void | T>;
6
+ };
7
+ /**
8
+ * Creates a derived (projected) store. Like `createMemo` but for stores: the
9
+ * derive function receives a mutable draft and either mutates it in place
10
+ * (canonical) or returns a new value. Either way the result is reconciled
11
+ * against the previous draft by `options.key` (default `"id"`), so surviving
12
+ * items keep their proxy identity — only added/removed items are
13
+ * created/disposed.
14
+ *
15
+ * Returns the projected store directly (no setter — reads only).
16
+ *
17
+ * Use this when you want the structural-sharing / per-property tracking
18
+ * behaviour of a store on top of a derived computation. For simple read-only
19
+ * derivations, `createMemo` is lighter.
20
+ *
21
+ * @param fn receives the current draft; mutate it in place or return new
22
+ * data. Return is convenient for filter/derive shapes where mutation is
23
+ * awkward.
24
+ * @param seed the backing store value to wrap and reconcile into
25
+ * @param options `ProjectionOptions` — `name`, `key`. `key` defaults to
26
+ * `"id"`; specify it only when your data uses a different identity field
27
+ * (e.g. `{ key: "uuid" }` or `{ key: u => u.slug }`).
28
+ *
29
+ * @example
30
+ * ```ts
31
+ * // Mutation form — update individual fields on the draft.
32
+ * const summary = createProjection<{ total: number; active: number }>(
33
+ * draft => {
34
+ * draft.total = users().length;
35
+ * draft.active = users().filter(u => u.active).length;
36
+ * },
37
+ * { total: 0, active: 0 }
38
+ * );
39
+ *
40
+ * // Return form — produce a derived collection. Reconciled by `id` so each
41
+ * // surviving user keeps the same store identity across recomputes.
42
+ * const activeUsers = createProjection<User[]>(
43
+ * () => allUsers().filter(u => u.active),
44
+ * []
45
+ * );
46
+ * ```
47
+ *
48
+ * @see {@link https://github.com/solidjs/x-reactivity#createprojection}
49
+ */
50
+ export declare function createProjection<T extends object = {}>(fn: (draft: T) => void | T | Promise<void | T> | AsyncIterable<void | T>, seed: Partial<T>, options?: ProjectionOptions): Refreshable<Store<T>>;
51
+ /**
52
+ * Shared projection computed body used by both `createProjection` and the derived
53
+ * form of `createOptimisticStore`. Encapsulates the write-trap draft, `storeSetter`
54
+ * wrapping, the `handleAsync` subscription with a setter callback, and the commit
55
+ * path (which must always go through `storeSetter` so the `writeOnly` guard is
56
+ * engaged during `reconcile`'s property reads).
57
+ *
58
+ * `wrapCommit` is invoked for every commit (sync return and each async yield) and
59
+ * lets callers layer extra context around the write — e.g. the optimistic store
60
+ * re-enters `setProjectionWriteActive` so reconciles target `STORE_OVERRIDE`
61
+ * instead of `STORE_OPTIMISTIC_OVERRIDE` even when an async yield fires outside
62
+ * the outer `setProjectionWriteActive` scope.
63
+ */
64
+ export declare function runProjectionComputed<T extends object>(wrappedStore: Store<T>, fn: (draft: T) => void | T | Promise<void | T> | AsyncIterable<void | T>, key: string | ((item: NonNullable<any>) => any), wrapCommit?: (write: () => void) => void): Computed<void | T>;
65
+ export declare function createWriteTraps(isActive?: () => boolean): ProxyHandler<any>;
66
+ export declare const writeTraps: ProxyHandler<any>;
@@ -0,0 +1,23 @@
1
+ /**
2
+ * Returns a draft-mutating function that smart-merges `value` into a store,
3
+ * preserving the identity of items whose `key` field matches between old and
4
+ * new states. Useful when applying server payloads or full-replacement data
5
+ * onto an existing store without losing fine-grained reactivity.
6
+ *
7
+ * Items with the same key are updated in place (only changed properties
8
+ * trigger updates). Items added or removed update the corresponding signals.
9
+ *
10
+ * @param value the next state to merge in
11
+ * @param key property name (string) or extractor function for stable identity
12
+ *
13
+ * @example
14
+ * ```ts
15
+ * const [todos, setTodos] = createStore<Todo[]>([]);
16
+ *
17
+ * async function refresh() {
18
+ * const fresh = await api.getTodos();
19
+ * setTodos(reconcile(fresh, "id")); // diff-merge by `id`
20
+ * }
21
+ * ```
22
+ */
23
+ export declare function reconcile<T extends U, U>(value: T, key: string | ((item: NonNullable<any>) => any)): (state: U) => void;