@solidjs/web 2.0.0-rc.15 → 2.0.0-rc.17

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 +1 -1
  2. package/dist/server.dev.js +361 -483
  3. package/dist/server.js +346 -391
  4. package/dist/server.observe.js +346 -391
  5. package/dist/web.dev.js +110 -55
  6. package/dist/web.js +51 -50
  7. package/dist/web.observe.js +61 -55
  8. package/frames/dist/client.dev.js +610 -621
  9. package/frames/dist/client.js +540 -566
  10. package/frames/dist/client.observe.js +571 -573
  11. package/frames/dist/regions.js +43 -2
  12. package/frames/dist/server.dev.js +793 -424
  13. package/frames/dist/server.js +792 -371
  14. package/frames/dist/server.observe.js +792 -371
  15. package/frames/dist/wire.js +371 -6
  16. package/package.json +11 -11
  17. package/serialization/dist/decode.js +9 -7
  18. package/serialization/dist/serialization.js +9 -7
  19. package/serialization/types/serializer-decode.d.ts +2 -2
  20. package/server-functions/dist/client.dev.js +13 -22
  21. package/server-functions/dist/client.js +11 -22
  22. package/server-functions/dist/client.observe.js +13 -22
  23. package/server-functions/dist/rich-args.js +84 -1
  24. package/server-functions/dist/server.dev.js +194 -20
  25. package/server-functions/dist/server.js +194 -20
  26. package/server-functions/dist/server.observe.js +194 -20
  27. package/skills/server-components/SKILL.md +74 -185
  28. package/types/client.d.ts +27 -5
  29. package/types/diagnostics.d.ts +16 -0
  30. package/types/frames/assets-tier.d.ts +2 -2
  31. package/types/frames/client.d.ts +8 -3
  32. package/types/frames/frame-client.d.ts +121 -157
  33. package/types/frames/frame-morph.d.ts +28 -0
  34. package/types/frames/frame-sink.d.ts +13 -9
  35. package/types/frames/frame-transport.d.ts +30 -1
  36. package/types/frames/regions-tier.d.ts +15 -0
  37. package/types/frames/serializer-decode.d.ts +2 -2
  38. package/types/frames/server.d.ts +0 -52
  39. package/types/frames/wire-tier.d.ts +54 -1
  40. package/types/index.d.ts +2 -2
  41. package/types/jsx.d.ts +11 -5
  42. package/types/observe.d.ts +14 -7
  43. package/types/render.d.ts +3 -1
  44. package/types/response.d.ts +5 -4
  45. package/types/serializer-decode.d.ts +2 -2
  46. package/types/server-functions/argument-codec.d.ts +30 -0
  47. package/types/server-functions/client.d.ts +27 -9
  48. package/types/server-functions/server.d.ts +23 -2
  49. package/types/server-functions/shared.d.ts +19 -0
  50. package/types/server-functions/uploads.d.ts +50 -0
  51. package/types/server-observe.d.ts +3 -2
  52. package/types/server.d.ts +58 -77
  53. package/frames/dist/bind.dev.js +0 -326
  54. package/frames/dist/bind.js +0 -295
  55. package/types/frames/bind-tier.d.ts +0 -60
@@ -1,228 +1,117 @@
1
+ ---
2
+ name: server-components
3
+ description: Rules for writing Solid 2.0 server components ("use server" functions that return a template) and their slots with @solidjs/web. Use when writing or reviewing a server component, deciding what lives on the server versus the client, or wiring a slot.
4
+ ---
5
+
1
6
  # Writing Solid server components with slots
2
7
 
3
8
  A Solid server component is a `"use server"` function that returns a
4
9
  template; the browser receives its markup and never its code. Anything the
5
- client contributes goes through a **slot** on the component's props. This
6
- guide is the set of rules an author — a person or an agent — needs to write
7
- one correctly the first time. The design record is
8
- `documentation/server-components/server-components-principles.md` §9.2.3;
9
- this file is the operative subset.
10
+ client contributes goes through a **slot** on the component's props: a
11
+ client component the client places at a position in the server's markup.
12
+ This guide is the set of rules an author — a person or an agent — needs to
13
+ write one correctly the first time. The design record is
14
+ `documentation/server-components/server-components-principles.md`; this
15
+ file is the operative subset.
10
16
 
11
17
  ## Where things go
12
18
 
13
19
  > **An element lives where the data that creates it lives.**
14
20
 
15
21
  - Exists because of **server data** (a todo row, a nav link, a search
16
- form the server renders)? It is **server markup**. Client behavior or a
17
- client-driven value on it is a **binding slot** — bind, never wrap.
18
- Do not wrap a server-rendered element in a client component to give it a
19
- handler or a class.
20
- - Exists because of **client state alone** (an optimistic add, a modal, a
21
- drag ghost, an editor open over a field)? It is a **client component**
22
- placed through a **template slot**.
22
+ form the server renders)? It is **server markup**. A mutation on it is a
23
+ form `action` — it works without JavaScript, and the router marks a
24
+ submission in flight (`aria-busy`) so CSS can show the intent.
25
+ - Needs **client behavior or client state** (a handler, an optimistic add,
26
+ a modal, a drag ghost, an editor open over a field)? It is a **client
27
+ component** placed through a **slot**.
23
28
 
24
29
  When the client confirms an optimistic entity and the server renders it, the
25
30
  row _becomes_ server markup; `$key` on the element reconciles the two.
26
31
 
27
- ## The two kinds of slot
32
+ ## Slots
28
33
 
29
34
  ```tsx
30
- import type { BindingSlot, Slot } from "@solidjs/web/frames";
35
+ import type { Slot } from "@solidjs/web/frames";
31
36
 
32
37
  interface TodosProps {
33
- pending: Slot; // template: the client returns JSX
34
- row: BindingSlot<{ id: string; completed: boolean }, RowBehavior>; // bindings: the client returns an object
35
- filters: BindingSlot<{}, FilterBehavior>; // no args: called bare
38
+ pending: Slot; // no props
39
+ editor: Slot<{ id: string; title: string }>; // props from the server
36
40
  }
37
41
  ```
38
42
 
39
- A **template slot** is placed as an element: `<props.pending />`. The client
40
- owns those nodes.
41
-
42
- A **binding slot** is _called_ once per data context and its properties
43
- are _bound_ at positions of the server's own template:
43
+ A slot is placed as an element: `<props.pending />`,
44
+ `<props.editor id={t.id} title={t.title} />`. The client owns the nodes
45
+ between the slot's markers; the server's markup around them stays the
46
+ server's.
44
47
 
45
48
  ```tsx
46
49
  export async function todoList() {
47
50
  "use server";
48
51
  const todos = await db.list();
49
- return (props: TodosProps) => {
50
- const filters = props.filters();
51
- return (
52
- <>
53
- <ul>
54
- {todos.map(t => (
55
- <TodoRow
56
- id={t.id}
57
- title={t.title}
58
- row={props.row({ id: t.id, completed: t.completed })}
59
- />
60
- ))}
61
- <props.pending />
62
- </ul>
63
- <a href="#/" class={{ selected: filters.all }}>
64
- All
65
- </a>
66
- </>
67
- );
68
- };
52
+ return (props: TodosProps) => (
53
+ <ul>
54
+ {todos.map(t => (
55
+ <li $key={t.id}>
56
+ {t.title}
57
+ <props.editor $key={t.id} id={t.id} title={t.title} />
58
+ </li>
59
+ ))}
60
+ <props.pending />
61
+ </ul>
62
+ );
69
63
  }
70
64
  ```
71
65
 
72
- The client passes the fill — a function of the args that returns the object:
66
+ The client passes the fill — a component of the slot's props:
73
67
 
74
68
  ```tsx
75
- <Todos row={rowFor} filters={() => ({ get all() { return filter() === "all"; }, … })} pending={() => <For each={adds}>{…}</For>} />
69
+ <Todos editor={p => <Editor id={p.id} title={p.title} />} pending={() => <For each={adds}>{…}</For>} />
76
70
  ```
77
71
 
78
- The fill must return a plain object. An array, a DOM node, a function or
79
- an async value is a type error on both sides (`BindingSlot`'s return is
80
- `SlotOutput<J>`, a branded `SlotError` naming the reason) and a
81
- `fill-shape` finding at runtime.
82
-
83
- ## The one rule for binding slots
84
-
85
- > **A slot property is a JSX attribute value or a text child, whole, and nothing else.**
86
-
87
- Legal positions: an attribute (`hidden={row.removed}`, `checked={row.done}`,
88
- `title={row.error}`), a class name inside object form
89
- (`class={{ completed: row.done }}`), the whole `class`/`style`
90
- (`class={row.rowClass}`), a style property (`style={{ opacity: row.fade }}`),
91
- an event (`onInput={row.onToggle}`), a ref (`ref={row.ref}`) — on an element
92
- with a spread too (`<button {...rest} onClick={row.go} />` — the last
93
- source that has the key wins, `undefined` included, as the client's
94
- spread reads it) — and a text child (`<strong>{list.remaining}</strong> items
95
- left`): a string or number renders, nullish and booleans render empty, and
96
- the client owns the text between a `<!--_s:t=…-->` marker pair. Never the
97
- content of `<textarea>`, `<title>`, `<style>` or `<script>`, where the
98
- markers would be literal text — bind `value=` or a style property there.
99
- Not a `prop:*` property, not inside another slot call's args (nested in
100
- plain objects and arrays included). Reserved keys the fill must not use:
101
- keys beginning with `$` or a digit, `length`, `slice`, `t`/`h`/`p`, `then`,
102
- `constructor`/`toString`/`valueOf`/`toJSON`; anything else (`filter`, `map`
103
- included) is a plain property.
104
-
105
- The server **does not have the value** — on the stream face a property read
106
- is a stand-in with no value, on the document face only the initial one — so
107
- nothing can be computed from it on the server. Every one of these is wrong:
108
-
109
- | Wrong | Why | Write instead |
110
- | ---------------------------------------------------------------------- | ------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------ |
111
- | ``class={`todo ${row.done}`}`` | stringified: not the whole value | `class={{ todo: true, completed: row.done }}` or return `rowClass` from the fill |
112
- | `row.count > 3 ? "a" : "b"` | comparison on a stand-in | decide in the fill; return the decided value |
113
- | `if (row.error) …`, `row.error && <button/>`, `<Show when={row.done}>` | truthiness: a stand-in is an object and **always truthy** — the branch always renders | presence → `hidden={…}` or a class; a node that exists because of client state → a template slot |
114
- | `<strong>{row.label}</strong>` where the fill returns JSX for `label` | a text position renders a string or number | a template slot for markup |
115
- | `<textarea>{row.draft}</textarea>` | raw-text content: the markers land in the text | `value={row.draft}` |
116
- | `format(row.title)` (a server helper) | the helper receives a stand-in | do the formatting in the fill |
117
- | `<li {...row}>` | spread: the template must show what the client owns | name each position |
118
- | `onClick={() => …}` on a server element | a server function can never run in the browser | bind a slot property or a form `action` |
119
- | `onKeyDown={[row.key, 1]}` | a tuple: a marker names keys, never data | return `onKeyDown: [handler, data]` from the fill; bind `onKeyDown={row.onKeyDown}` |
120
-
121
- Every case except truthiness and raw-text content is a dev finding
122
- (`BINDING_SLOT_POSITION`) and renders **nothing on either face**, so it
123
- shows on the first render. Truthiness has no runtime hook: if a retry button
124
- appears on every row, this is why. Raw-text content has none either; in
125
- `<textarea>` and `<title>` the markers show as text.
126
-
127
- ## Writing the fill
128
-
129
72
  - **The fill runs once per occurrence, as a component body does.** It runs
130
- untracked, under the occurrence's owner, with live args. State it
73
+ untracked, under the occurrence's owner, with live props. State it
131
74
  creates (a signal, a memo, an `onCleanup`) lives as long as the
132
75
  occurrence. A top-level read is read once, and `STRICT_READ_UNTRACKED`
133
- names it.
134
- - **Values as getters, handlers as plain closures.** A getter is the
135
- reactive form, as on a component's props object; a plain value never
136
- updates:
137
-
138
- ```tsx
139
- const rowFor = (p: { id: string; completed: boolean }): RowBehavior => ({
140
- get rowClass() {
141
- return { todo: true, completed: done(p.id, p.completed), pending: !!intent.byId[p.id] };
142
- },
143
- get done() {
144
- return done(p.id, p.completed);
145
- },
146
- get removed() {
147
- return removed(p.id);
148
- },
149
- onToggle: e => actions.toggle(p.id, e.currentTarget.checked),
150
- onRemove: () => actions.remove(p.id)
151
- });
152
- ```
153
-
154
- Each getter is read where its position binds, so a change moves the
155
- positions that read it. The same object serves a client
156
- `<TodoRow row={rowFor(todo)} />`, whose body reads it the same way. A
157
- plain value is right only for what never changes (a constant handler,
158
- a fixed class).
159
-
160
- - **Name it like a props interface**, because it is one (a shared component
161
- takes it as a prop). Handlers are `on` + intent — `onToggle`, `onRemove`,
162
- `onCopy`, `onClearCompleted`; the position names the DOM event, the key
163
- names the meaning, as a component's `onSelect` does. Values are nouns or
164
- adjectives (`done`, `rowClass`, `error`, `busy`); a ref is `ref`. The
165
- runtime reads nothing into the prefix — the position decides what a
166
- property is — but a reader can tell a handler from a value without
167
- opening the type.
168
- - Handlers and refs are read once, when an element binds, and bind as in
169
- client JSX: delegated events delegate, a `[handler, data]` tuple returned
170
- from the fill binds as a tuple, a ref fires once per element. A handler
171
- behind a getter is read once, as `onClick={cond() ? a : b}` is.
172
- - **`$key` is optional.** A call repeated within a render (a component
173
- prop re-evaluates it per position) is one occurrence either way. Add
174
- `$key: t.id` when the fill holds its own state (an edit draft, a signal
175
- created inside) that must follow the entity across refetches and
176
- reorders. Values never depend on it.
177
- - Reserved keys in the returned object: anything beginning with `$`, the
178
- node keys `t` `h` `p` `then`, and `Object`/`Array` prototype member names
179
- (`length`, `map`, …).
76
+ names it ("the \`editor\` template-slot fill").
77
+ - **Place slots as JSX, not calls.** The compiler wraps each prop in a
78
+ getter so the read defers to the slot border; a call form
79
+ (`props.status({ … })`) evaluates its args eagerly in the server
80
+ component's body.
81
+ - **`$key` is optional.** Add it when the fill holds its own state (an edit
82
+ draft, a signal created inside) that must follow the entity across
83
+ refetches and reorders.
84
+ - **An async value crosses with `asyncArg`.**
85
+ `<props.status progress={asyncArg(gen.progress)} />` ships the promise or
86
+ async iterable; the fill's read settles (suspends until the first value).
87
+
88
+ ## Behavior on server markup
89
+
90
+ A handler on a server-rendered element cannot come from the server: a
91
+ server function never runs in the browser. Pick one:
92
+
93
+ - **A form.** A mutation is `<form action={…}>`; it works before
94
+ JavaScript and needs no client code.
95
+ - **A client component that owns the element.** Move the control into a
96
+ slot's fill (`<props.toggle id={t.id} done={t.completed} />`, rendering
97
+ the checkbox on the client).
98
+ - **One delegated listener.** For many identical controls inside server
99
+ markup (a copy button on every code block), place one slot occurrence
100
+ whose component registers a single document listener in `onSettled` and
101
+ finds its target from the event (`closest("button.copy-code")`). Inside a
102
+ live hole this is the shape that keeps the hole streaming: a slot placed
103
+ inside a live hole latches it (`SSR_LIVE_HOLE_LATCHED`, `data.cause`
104
+ `"records"`). `examples/chat`'s Copy button is this shape.
180
105
 
181
106
  ## Shared components
182
107
 
183
- One component can render on both sides: on the server its `row` prop is
184
- the binding slot's return, on the client it is the fill's result. It
185
- cannot tell and need not. Put `$key={props.id}` on the element it renders
186
- (morph identity) — the slot call's own `$key` is a different key for a
187
- different job. Do not read `document`/`window` during render; that is the
188
- ordinary isomorphic rule.
108
+ One component can render on both sides. Put `$key={props.id}` on the
109
+ element it renders (morph identity) — the slot's own `$key` is a different
110
+ key for a different job. Do not read `document`/`window` during render;
111
+ that is the ordinary isomorphic rule.
189
112
 
190
113
  ## Compiling
191
114
 
192
- Server components need the SSR compile with the `serverComponents` compiler
193
- option. With `@solidjs/vite-plugin`, `solid({ ssr: true, serverFunctions:
115
+ With `@solidjs/vite-plugin`, `solid({ ssr: true, serverFunctions:
194
116
  { components: true } })` is the turnkey setup (the examples under
195
- `examples/todos-server`, `examples/notes`, `examples/chat`); a hand-rolled
196
- build passes `serverComponents: true` to `@solidjs/compiler` or
197
- `@solidjs/babel-plugin` for the SSR side. Without it a dynamic
198
- `class`/`style` compiles inside the template's quotes, where a slot value
199
- cannot be marked — the `inline` finding below.
200
-
201
- ## Diagnostics
202
-
203
- `BINDING_SLOT_POSITION` (`data.reason`):
204
-
205
- | reason | severity | what happened | fix |
206
- | -------------- | -------------- | ----------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------- |
207
- | `spread` | error (throws) | a slot's return was spread onto an element | name each position |
208
- | `stringified` | warn | template literal / concatenation | whole value at one position |
209
- | `coerced` | warn | comparison, arithmetic, `==` | decide in the fill |
210
- | `inline` | warn | reached `class`/`style` inside template quotes | compile with `serverComponents: true` |
211
- | `markup` | warn | the fill returned JSX but the template read a property | return an object, or place the slot |
212
- | `server-local` | warn | a server function at `on*`/`ref` | bind a slot property |
213
- | `tuple` | warn | an array at an `on*` position | return the tuple from the fill |
214
- | `reserved-key` | warn | the fill used a reserved key | rename it |
215
- | `arg` | warn | a slot property passed in another slot call's argument (nested in plain objects/arrays; `data.path`) | pass the server's own value, or read it in the fill from client state |
216
- | `prop` | warn | a slot property at a `prop:*` key of a spread | bind the attribute form, or set the property in the fill's ref |
217
- | `fill-shape` | warn (client) | the fill returned a non-object (`null`, array, DOM node, async value, primitive), or the prop read as data is not a function | return a plain object from a function prop |
218
- | `text-shape` | warn (client) | a text position received a non-primitive (object, array, DOM node, function, async value — `data.key`, `data.shape`) | return a string or number; markup goes in a template slot |
219
- | `orphan` | warn (client) | markers for an occurrence that can never bind: `data.why` `"fill"` — no fill for the prop; `"record"` — a called occurrence with no args record | `fill`: pass the prop / match the name on both sides. `record`: not the fill — rebuild client and server together (stale prebundle, cached asset), else report it |
220
-
221
- Every reason but `fill-shape`, `text-shape` and `orphan` comes from the server render.
222
- `orphan` is the one failure this model cannot otherwise show you: the
223
- element is inert — a handler that never fires, a class that never updates —
224
- with no error.
225
-
226
- `STRICT_READ_UNTRACKED` naming a fill ("the \`row\` binding-slot fill",
227
- "the \`comment\` template-slot fill"): a top-level read in its body; use
228
- getters (above).
117
+ `examples/todos-server`, `examples/notes`, `examples/chat`).
package/types/client.d.ts CHANGED
@@ -126,7 +126,7 @@ export declare function takeHydrationValue<T = unknown>(key: string): HydrationV
126
126
  * Client stub — a render's link handler is set during server rendering
127
127
  * (see the server entry's `setLinkClaim`). Always `false` here, so a router
128
128
  * can call it unguarded from isomorphic setup code.
129
- * @experimental
129
+ * @internal
130
130
  */
131
131
  export declare function setLinkClaim(_handler: LinkClaimHandler | undefined): boolean;
132
132
  /**
@@ -137,7 +137,7 @@ export declare function setLinkClaim(_handler: LinkClaimHandler | undefined): bo
137
137
  * and after hydration. `false` on a page rendered without the router — the
138
138
  * absence of link state on an anchor then means nothing, and a link
139
139
  * consumer must resolve it itself. Server: `false`.
140
- * @experimental
140
+ * @internal
141
141
  */
142
142
  export declare function hasServerLinkState(): boolean;
143
143
  /**
@@ -203,7 +203,22 @@ export declare function unregisterDelegatedContainer(container: MountableElement
203
203
  export declare function dispatchAsInteraction<T>(e: Event, fn: () => T): T;
204
204
  export declare function getDelegatedRoot(node: MountableElement): MountableElement | undefined;
205
205
  export declare function setProperty(node: Element, name: string, value: any): void;
206
- /** Options for `registerElementClaim`. */
206
+ /**
207
+ * A stateful DOM property write (`input.value`, `input.checked`,
208
+ * `option.selected`, `video.muted`, ...) from dev-compiled, non-hydratable
209
+ * DOM output: exactly `node[name] = value`, which is what production
210
+ * output inlines. The dev runtime checks it first and warns
211
+ * (`UNCOMMITTED_INPUT_OVERWRITTEN`) when it re-applies an unchanged bound
212
+ * value over an edit the user never committed to the signal. Production
213
+ * compile output never imports it, so it tree-shakes away.
214
+ *
215
+ * @internal Compiler output only.
216
+ */
217
+ export declare function setStatefulProperty(node: Element, name: string, value: any): void;
218
+ /**
219
+ * Options for `registerElementClaim`.
220
+ * @internal
221
+ */
207
222
  export type ElementClaimOptions = {
208
223
  /**
209
224
  * Attribute names whose compiler-owned writes re-claim an already claimed
@@ -272,8 +287,8 @@ export declare function style(node: Element, value: {
272
287
  export declare function readShallow(value: unknown): unknown;
273
288
  /** Compiler-emitted primitive; not for hand-written code. @internal */
274
289
  export declare function setStyleProperty(node: Element, name: string, value: any): void;
275
- export declare function spread(node: Element, sources: unknown[], skipChildren?: Boolean, skip?: (key: string) => boolean, name?: string): void;
276
- export declare function spread<T>(node: Element, accessor: T, skipChildren?: Boolean, skip?: (key: string) => boolean, name?: string): void;
290
+ export declare function spread(node: Element, sources: unknown[], skipChildren?: Boolean, skip?: (key: string) => boolean, name?: string, loc?: string): void;
291
+ export declare function spread<T>(node: Element, accessor: T, skipChildren?: Boolean, skip?: (key: string) => boolean, name?: string, loc?: string): void;
277
292
  export declare function dynamicProperty(props: unknown, key: string): unknown;
278
293
  export declare function applyRef<T extends Element = Element>(r: ((element: NoInfer<T>) => void) | ((element: NoInfer<T>) => void)[], element: T): void;
279
294
  export declare function ref(fn: () => ((element: Element) => void) | ((element: Element) => void)[], element: Element): void;
@@ -300,6 +315,13 @@ export declare function insert<T>(parent: MountableElement, accessor: (() => T)
300
315
  * observe runtimes carry it on the node; production ignores it.
301
316
  */
302
317
  name?: string;
318
+ /**
319
+ * Source location of the hole (`src/App.tsx:14:7`, root-relative
320
+ * `file:line:col`) — the compiler's `sourceNames` `locations` kind. Dev
321
+ * and observe runtimes carry it on the node for console reports and
322
+ * diagnostic events; production ignores it.
323
+ */
324
+ loc?: string;
303
325
  }): JSX.Element;
304
326
  export declare function assign(node: Element, props: any, skipChildren?: Boolean, prevProps?: any, skipRef?: Boolean): void;
305
327
  export declare function warmAsset(descriptor: AssetDescriptor): AssetEntry | undefined;
@@ -60,5 +60,21 @@ export declare function unscopedHoleAllocatedIds(before: string, after: string,
60
60
  * text. Reported once per attribute name so a row template reports once.
61
61
  */
62
62
  export declare function lowercaseEventAttribute(name: string, node: Element): void;
63
+ /**
64
+ * Dev CHECK, before every compiled or spread write of a stateful DOM
65
+ * property (`input.value`, `input.checked`, `option.selected`,
66
+ * `video.muted`, ...): Solid is about to write the same value it wrote last
67
+ * time, but the element no longer holds what that write left there. Nothing
68
+ * Solid wrote changed it, so the user did — typed, clicked, toggled — and
69
+ * that edit never reached the bound signal; the write is about to erase it.
70
+ * The write re-applies an unchanged value because the binding re-ran
71
+ * without its value changing: another binding in the same template effect
72
+ * changed, a spread re-ran, or the source fired with an equal value
73
+ * (`equals: false`). Warns once per element and property; the write itself
74
+ * goes ahead unchanged. Pair with `recordStatefulWrite` after the write.
75
+ */
76
+ export declare function checkStatefulWrite(node: Element, prop: string, value: unknown): void;
77
+ /** Dev: remembers what a stateful write left on the element (see `checkStatefulWrite`). */
78
+ export declare function recordStatefulWrite(node: Element, prop: string, value: unknown): void;
63
79
  /** `Name: message` for an Error, `String(value)` otherwise. */
64
80
  export declare function errorText(error: unknown): string;
@@ -10,8 +10,8 @@
10
10
  * `applyInlineStyles`, `findHeadElement`'s attribute-compared lookup and
11
11
  * head.ts's `qualifierValue`), the per-frame flush a pending stylesheet
12
12
  * wakes, and the assets pass over a record (modules, typed preloads, inline
13
- * styles). The eager client keeps the record itself (`chunkToRecords`'
14
- * `assets` case, the host's `seg::assets` accumulate), the pass's walk over
13
+ * styles). The eager client keeps the record itself (the wire's
14
+ * `seg:<k>:assets` record, the host's `seg::assets` accumulate), the pass's walk over
15
15
  * the store, and the reveal's READINESS TERM: a segment whose assets record
16
16
  * carries stylesheets or inline styles while this tier is not resident is
17
17
  * not ready — the server's `<Loading>` fallback stays on screen; the reveal
@@ -1,10 +1,8 @@
1
1
  import { type TierModule } from "./frame-client.js";
2
2
  export { createFrame, createFrameHost, createFrameElement, FRAME_APPLIED_EVENT } from "./frame-client.js";
3
3
  export type { TierModule } from "./frame-client.js";
4
- /** @internal */
5
- export { isAsyncValue } from "./frame-client.js";
6
4
  export { FRAME_STREAM_HEADER, applyFrameResponse, isFrameStreamResponse, createServerComponentHandler } from "./frame-transport.js";
7
- export type { Slot, BindingSlot, SlotOutput, SlotError } from "./server.js";
5
+ export type { Slot } from "./server.js";
8
6
  /**
9
7
  * Client-condition twin of the server face's `asyncArg` (DR-2 value tier):
10
8
  * the identity that types an async value crossing the slot border as its
@@ -20,6 +18,13 @@ export declare function asyncArg<T>(value: PromiseLike<T> | AsyncIterable<T>): T
20
18
  * @experimental
21
19
  */
22
20
  export declare function getFrameHost(): any;
21
+ /**
22
+ * Turn deferred hydration off (or back on) for the frames this client
23
+ * adopts from now on: off, an adopted occurrence mounts in the adoption
24
+ * pass. A test seam for the specs that pin adoption-time ordering.
25
+ * @internal
26
+ */
27
+ export declare function setDeferredHydration(on: boolean): void;
23
28
  /**
24
29
  * Options for `installServerComponents`.
25
30
  * @experimental