@verajs/renderer 0.1.5 → 0.2.1
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.
- package/README.md +1063 -27
- package/dist/development/vera-renderer-hydrate.d.ts +32 -13
- package/dist/development/vera-renderer-hydrate.d.ts.map +1 -1
- package/dist/development/vera-renderer-hydrate.js +1959 -269
- package/dist/development/vera-renderer-hydrate.js.map +1 -1
- package/dist/development/vera-renderer-keyed.d.ts +17 -0
- package/dist/development/vera-renderer-keyed.d.ts.map +1 -0
- package/dist/development/vera-renderer-keyed.js +322 -0
- package/dist/development/vera-renderer-keyed.js.map +1 -0
- package/dist/development/vera-renderer-profiler.d.ts +57 -17
- package/dist/development/vera-renderer-profiler.d.ts.map +1 -1
- package/dist/development/vera-renderer-profiler.js +1592 -244
- package/dist/development/vera-renderer-profiler.js.map +1 -1
- package/dist/development/vera-renderer-slots.d.ts +103 -0
- package/dist/development/vera-renderer-slots.d.ts.map +1 -0
- package/dist/development/vera-renderer-slots.js +1387 -0
- package/dist/development/vera-renderer-slots.js.map +1 -0
- package/dist/development/vera-renderer-spread.d.ts +41 -0
- package/dist/development/vera-renderer-spread.d.ts.map +1 -0
- package/dist/development/vera-renderer-spread.js +633 -0
- package/dist/development/vera-renderer-spread.js.map +1 -0
- package/dist/development/vera-renderer-tag.d.ts +61 -0
- package/dist/development/vera-renderer-tag.d.ts.map +1 -0
- package/dist/development/vera-renderer-tag.js +829 -0
- package/dist/development/vera-renderer-tag.js.map +1 -0
- package/dist/development/vera-renderer.d.ts +41 -16
- package/dist/development/vera-renderer.d.ts.map +1 -1
- package/dist/development/vera-renderer.js +1522 -235
- package/dist/development/vera-renderer.js.map +1 -1
- package/dist/vera-renderer-hydrate.min.js +1 -1
- package/dist/vera-renderer-hydrate.min.js.map +1 -1
- package/dist/vera-renderer-keyed.min.js +2 -0
- package/dist/vera-renderer-keyed.min.js.map +1 -0
- package/dist/vera-renderer-slots.min.js +2 -0
- package/dist/vera-renderer-slots.min.js.map +1 -0
- package/dist/vera-renderer-spread.min.js +2 -0
- package/dist/vera-renderer-spread.min.js.map +1 -0
- package/dist/vera-renderer-tag.min.js +2 -0
- package/dist/vera-renderer-tag.min.js.map +1 -0
- package/dist/vera-renderer.min.js +1 -1
- package/dist/vera-renderer.min.js.map +1 -1
- package/package.json +24 -1
|
@@ -1,3 +1,86 @@
|
|
|
1
|
+
/**
|
|
2
|
+
* `true ` only: the one home for *"is this value something an attribute can carry?"*
|
|
3
|
+
*
|
|
4
|
+
* **Why it is a closed vocabulary and not a predicate.** The first design asked whether a value
|
|
5
|
+
* stringifies meaningfully — `String(v) === '[object Object]'` means it lost its data. Driven
|
|
6
|
+
* through 16 value shapes rather than reasoned about, that broke four ways, and the first is
|
|
7
|
+
* disqualifying: `String()` THROWS on `Object.create(null)`, on `{ toString: null }`, and on any
|
|
8
|
+
* object whose `toString` throws — so a diagnostic would have killed the page for an author using
|
|
9
|
+
* the recommended dictionary idiom. It also passed `["a","b"]` as `"a,b"` (one junk class, if that
|
|
10
|
+
* was a `class` binding) and `new Date()` as a timezone-bearing string, which is an SSR/CSR
|
|
11
|
+
* divergence manufactured out of correct-looking code. And it passed `Symbol('s')` while
|
|
12
|
+
* `` `${sym}` `` throws — a guard and its sink disagreeing about a single expression.
|
|
13
|
+
*
|
|
14
|
+
* "Does it stringify meaningfully" is an OPEN predicate over an unbounded, environment-dependent
|
|
15
|
+
* space, and open predicates cannot be audited. So the test is inverted and closed: **primitives
|
|
16
|
+
* pass; everything else is reported; anything else that should pass is a named row added on
|
|
17
|
+
* evidence.** The list has exactly one member so far.
|
|
18
|
+
*
|
|
19
|
+
* Credit where it is due: the four breaks were found by the omni engine's session, which drove the
|
|
20
|
+
* shapes rather than arguing about them, and the closed-vocabulary form is theirs.
|
|
21
|
+
*/
|
|
22
|
+
/**
|
|
23
|
+
* Blessed non-primitives — types whose `toString` IS the value the author means.
|
|
24
|
+
*
|
|
25
|
+
* Tested by brand rather than `instanceof`, which is false across realms: a `URL` built in an
|
|
26
|
+
* iframe is not `instanceof` the parent's `URL`, and a diagnostic that fires on a correct value in
|
|
27
|
+
* one frame and not another is worse than none.
|
|
28
|
+
*/
|
|
29
|
+
const brand = (value) => Object.prototype.toString.call(value);
|
|
30
|
+
/** One message per element+name+kind, so a value rebuilt every render does not flood the console. */
|
|
31
|
+
let reported;
|
|
32
|
+
/**
|
|
33
|
+
* Returns the complaint, or `null` when the value is fine. Never throws — the shapes that break a
|
|
34
|
+
* naive guard are exactly the ones worth reporting, so they reach the `object` arm and are named.
|
|
35
|
+
*/
|
|
36
|
+
const attributeValueComplaint = (tag, name, value) => {
|
|
37
|
+
const type = typeof value;
|
|
38
|
+
if (type === 'string' || type === 'number' || type === 'boolean' || type === 'bigint')
|
|
39
|
+
return null;
|
|
40
|
+
if (type === 'object' && brand(value) === '[object URL]')
|
|
41
|
+
return null;
|
|
42
|
+
/**
|
|
43
|
+
* Keyed by BRAND, not by `typeof` — `Date`, `Array` and a plain object are all `'object'`, so a
|
|
44
|
+
* coarser key reported whichever arrived first and silently swallowed the rest. An author who
|
|
45
|
+
* fixed the Date would never have been told about the array.
|
|
46
|
+
*/
|
|
47
|
+
const key = `${tag}|${name}|${type === 'object' ? brand(value) : type}`;
|
|
48
|
+
reported ??= new Set();
|
|
49
|
+
if (reported.has(key))
|
|
50
|
+
return null;
|
|
51
|
+
reported.add(key);
|
|
52
|
+
/**
|
|
53
|
+
* A function into an attribute is never what the author meant, but the REASON matters: on a
|
|
54
|
+
* custom element the Lit-era convention is that complex values are set as properties, so
|
|
55
|
+
* `<my-chart formatter={fn}>` is a coherent intention that this sink simply cannot express. The
|
|
56
|
+
* message names the binding that can, rather than blaming the author.
|
|
57
|
+
*/
|
|
58
|
+
const said = type === 'function'
|
|
59
|
+
? `a function, which becomes its own SOURCE TEXT`
|
|
60
|
+
: type === 'symbol'
|
|
61
|
+
? `a symbol, which every DOM conversion refuses`
|
|
62
|
+
: Array.isArray(value)
|
|
63
|
+
? `an array, which becomes its members joined by commas`
|
|
64
|
+
: brand(value) === '[object Date]'
|
|
65
|
+
? `a Date, whose text carries the TIMEZONE of whichever side rendered it`
|
|
66
|
+
: `an ${type}, which cannot survive as text`;
|
|
67
|
+
/**
|
|
68
|
+
* Returned WITHOUT the `[vera]` prefix, which each call site writes as a literal.
|
|
69
|
+
* `tests/diagnostics-convention.test.mjs` reads the prefix off the call, so a message handed over
|
|
70
|
+
* as a variable is invisible to it — and its answer to that is an allowance list. Taking the
|
|
71
|
+
* allowance would have excused these two calls rather than checked them, which is the
|
|
72
|
+
* reclassification this audit keeps refusing; the literal at the call site is what every other
|
|
73
|
+
* diagnostic in the repo does anyway.
|
|
74
|
+
*/
|
|
75
|
+
return (`renderer: the attribute \`${name}\` on <${tag}> was given ${said}. ` +
|
|
76
|
+
`An attribute value is a string and nothing else.\n` +
|
|
77
|
+
`If the element is meant to RECEIVE this value, bind a property instead — \`.${name}=\${value}\` ` +
|
|
78
|
+
`— which is how a custom element takes anything that is not text. If it is meant to be read as ` +
|
|
79
|
+
`text, convert it where you know what it means: \`date.toISOString()\`, \`list.join(' ')\`. ` +
|
|
80
|
+
`A Date in particular serializes with the SERVER's timezone on one side and the browser's on ` +
|
|
81
|
+
`the other, so it will not survive hydration.`);
|
|
82
|
+
};
|
|
83
|
+
|
|
1
84
|
/**
|
|
2
85
|
* @verajs/renderer — a ground-up, keyed, template-identity renderer.
|
|
3
86
|
*
|
|
@@ -57,18 +140,6 @@
|
|
|
57
140
|
* deliberately do not match the pattern: the first is an interop wire format, the second is called
|
|
58
141
|
* by the DOM itself.
|
|
59
142
|
*/
|
|
60
|
-
/**
|
|
61
|
-
* Marks a template result with a stable key so list reconciliation moves it instead of rewriting
|
|
62
|
-
* it. Key all items in a list or none — mixing is undefined behaviour, as are duplicate keys.
|
|
63
|
-
*
|
|
64
|
-
* ```js
|
|
65
|
-
* rows.map((r) => keyed(r.id, html`<tr>...</tr>`))
|
|
66
|
-
* ```
|
|
67
|
-
*/
|
|
68
|
-
const keyed = (key, result) => {
|
|
69
|
-
result.key = key;
|
|
70
|
-
return result;
|
|
71
|
-
};
|
|
72
143
|
/**
|
|
73
144
|
* Preserves the DOM of templates a child position toggles away from, instead of destroying it —
|
|
74
145
|
* form values, scroll positions and media playback survive the round trip (lit-html calls this
|
|
@@ -77,12 +148,22 @@ const keyed = (key, result) => {
|
|
|
77
148
|
* ```js
|
|
78
149
|
* html`<div>${hold(editing ? editor() : viewer())}</div>`
|
|
79
150
|
* ```
|
|
151
|
+
*
|
|
152
|
+
* **Anything that is not a template passes straight through.** There is nothing to park for a
|
|
153
|
+
* string, a list, `null` or `false`, and the branch that produces one is the ordinary shape of the
|
|
154
|
+
* expression this wraps — `hold(editing && editor())`, `hold(row ?? null)`. Wrapping those handed
|
|
155
|
+
* the renderer a `{ $h }` carrying a non-template, which reached the held-commit path and threw on
|
|
156
|
+
* `result.strings`: a whole render lost, from a value the same expression renders happily one
|
|
157
|
+
* character to the left. Decided here rather than in the renderer so the hot path pays nothing.
|
|
80
158
|
*/
|
|
81
|
-
const hold = (result) =>
|
|
159
|
+
const hold = (result) => result != null && typeof result === 'object' && isTemplateResult(result)
|
|
160
|
+
? { $h: result }
|
|
161
|
+
: result;
|
|
82
162
|
/**
|
|
83
163
|
* Unique per module load, so user text can never collide with it. Randomness here cannot break
|
|
84
164
|
* template caching — the marker only ever pairs a scan with its own Template construction.
|
|
85
165
|
*/
|
|
166
|
+
|
|
86
167
|
const MARKER = '$v' + ((Math.random() * 1e9) >>> 0).toString(36) + '$';
|
|
87
168
|
/** `<?xyz>` parses as a bogus comment whose data is `?xyz`. */
|
|
88
169
|
const MARKER_COMMENT_DATA = '?' + MARKER;
|
|
@@ -103,7 +184,37 @@ const markerWalker = doc.createTreeWalker(doc, 129 /* ELEMENT | COMMENT */);
|
|
|
103
184
|
* TreeWalker allocation per instance, which is 10 000 allocations in a 10 000-row create.
|
|
104
185
|
*/
|
|
105
186
|
const instanceWalker = doc.createTreeWalker(doc, 5 /* ELEMENT | TEXT */);
|
|
106
|
-
|
|
187
|
+
/**
|
|
188
|
+
* Elements whose children a parser reads as **text**, so a marker written inside one arrives as
|
|
189
|
+
* characters rather than a comment and the binding never becomes a part.
|
|
190
|
+
*
|
|
191
|
+
* `iframe` and `noscript` were missing, and both were measured broken in a browser rather than
|
|
192
|
+
* reasoned about: `html\`<iframe>${v}</iframe>\`` painted the literal marker — `<?$v8hpsho$>` — onto
|
|
193
|
+
* the page in **all three engines** and never updated.
|
|
194
|
+
*
|
|
195
|
+
* **`noscript` is the one worth the comment, because the engines disagree.** A template's contents
|
|
196
|
+
* are parsed with the scripting flag *disabled*, which is what decides whether `noscript` is raw
|
|
197
|
+
* text — and Chromium and WebKit parse it as markup there while Firefox parses it as text. So
|
|
198
|
+
* `html\`<noscript>${v}</noscript>\`` worked in two engines and painted the marker in the third: an
|
|
199
|
+
* app developed in Chrome shipping the framework's internals onto the page for Firefox users.
|
|
200
|
+
*
|
|
201
|
+
* Listing it here is safe in both parses. Where the marker became a comment the raw-text branch does
|
|
202
|
+
* not trigger, because it looks for the marker in `textContent` and finds none.
|
|
203
|
+
*/
|
|
204
|
+
const RAW_TEXT_TAGS = /^(?:script|style|textarea|title|iframe|noscript)$/i;
|
|
205
|
+
/**
|
|
206
|
+
* The void elements, as a regex rather than the `Set` in `@verajs/shared-utils`, and NOT imported
|
|
207
|
+
* from it — measured: an imported `new Set([...])` survives production because neither rollup nor
|
|
208
|
+
* terser can prove the constructor call is side-effect-free, so it sat at module scope costing
|
|
209
|
+
* **62 B gzipped on the base bundle** for a diagnostic production does not even run. A regex
|
|
210
|
+
* literal read only by `warnTagShape` goes when that dead function goes.
|
|
211
|
+
*
|
|
212
|
+
* So this is a second home for a fact `@verajs/shared-utils` owns, kept deliberately and in a
|
|
213
|
+
* different SHAPE because a hot file's byte budget forbids the shared one. That is only acceptable
|
|
214
|
+
* with an enforcer: `tests/markup-grammar-homes.test.mjs` drives this regex and the canonical set
|
|
215
|
+
* against each other, member by member, in both directions.
|
|
216
|
+
*/
|
|
217
|
+
const VOID_TAGS = /^(?:area|base|br|col|embed|hr|img|input|link|meta|param|source|track|wbr)$/i;
|
|
107
218
|
const ATTR_NAME_DELIMITER = /[\s"'>=/]/;
|
|
108
219
|
/** What an expression position turned out to be. */
|
|
109
220
|
const CHILD = 0;
|
|
@@ -123,7 +234,31 @@ const IN_BOUND_VALUE = 5; // collecting a bound attribute's statics
|
|
|
123
234
|
* A small state machine rather than tail regexes, because `>` inside quoted attribute values and
|
|
124
235
|
* inside comments must not terminate a tag, and raw-text elements swallow markup.
|
|
125
236
|
*/
|
|
126
|
-
|
|
237
|
+
/**
|
|
238
|
+
* `true ` only: the two ways a hand-written template describes a tree the parser will not build.
|
|
239
|
+
*
|
|
240
|
+
* `@verajs/jsx` normalises both at compile time, so this is the channel for the BUILDLESS path —
|
|
241
|
+
* which is this framework's baseline, not its fallback, and was the surface left broken when the
|
|
242
|
+
* compiler fix landed. It reaches the browser console on the client and during hydration; a
|
|
243
|
+
* server-only render never runs this scanner, so an SSR page that is never hydrated is not covered.
|
|
244
|
+
*
|
|
245
|
+
* The self-close test is `markup` ending in `/`, which is the same approximation the raw-text
|
|
246
|
+
* branch below already makes: an unquoted attribute value ending in a slash (`<div data-x=a/>`)
|
|
247
|
+
* reads the same way. That is not a false positive in any way that matters — measured, such a tag
|
|
248
|
+
* is an OPEN tag too and swallows what follows it exactly as `<div/>` does, so both the warning and
|
|
249
|
+
* the fix it names are correct for it.
|
|
250
|
+
*/
|
|
251
|
+
const warnTagShape = (tag, closing, selfClosed) => {
|
|
252
|
+
if (!closing && selfClosed && !VOID_TAGS.test(tag))
|
|
253
|
+
console.warn(`[vera] renderer: <${tag}> is left OPEN by this template, so everything after it becomes its ` +
|
|
254
|
+
`child rather than its sibling. HTML has no self-closing syntax outside <svg> and <math> — ` +
|
|
255
|
+
`\`<${tag} />\` is an open tag, not an empty element. Write \`<${tag}></${tag}>\`. ` +
|
|
256
|
+
`(@verajs/jsx rewrites this for you; a hand-written template has to say it.)`);
|
|
257
|
+
else if (closing && VOID_TAGS.test(tag))
|
|
258
|
+
console.warn(`[vera] renderer: \`</${tag}>\` is read by the parser as ANOTHER <${tag}>, so this template ` +
|
|
259
|
+
`renders two where it describes one. A void element has no end tag — write \`<${tag}>\` alone.`);
|
|
260
|
+
};
|
|
261
|
+
const scan = (strings, type = 1) => {
|
|
127
262
|
const specs = [];
|
|
128
263
|
let markup = '';
|
|
129
264
|
let state = IN_TEXT;
|
|
@@ -132,6 +267,16 @@ const scan = (strings) => {
|
|
|
132
267
|
let rawTag = ''; // which raw-text element we are inside
|
|
133
268
|
let tagNameStart = 0; // markup index where the current tag's name begins
|
|
134
269
|
let isClosing = false;
|
|
270
|
+
/**
|
|
271
|
+
* `true ` only. Depth of `<svg>`/`<math>` nesting, because foreign content is the one place the
|
|
272
|
+
* parser DOES honour XML self-closing, so neither warning applies inside it. An `svg`/`mathml`
|
|
273
|
+
* template is already inside one, hence the seed from `type`.
|
|
274
|
+
*
|
|
275
|
+
* `<foreignObject>` re-enters HTML content and is deliberately not tracked: suppressing a warning
|
|
276
|
+
* there is a missed warning, while tracking it wrongly would be a wrong one, and a diagnostic
|
|
277
|
+
* that cries wolf is worse than one that stays quiet.
|
|
278
|
+
*/
|
|
279
|
+
let foreign = type === 1 ? 0 : 1;
|
|
135
280
|
let attrName = '';
|
|
136
281
|
let statics = [];
|
|
137
282
|
let pending = ''; // the static chunk currently being collected IN_BOUND_VALUE
|
|
@@ -158,7 +303,9 @@ const scan = (strings) => {
|
|
|
158
303
|
statics.push(pending);
|
|
159
304
|
const quoteChar = quote || '"';
|
|
160
305
|
markup += ` ${specs.length}${MARKER}=${quoteChar}${statics.join(MARKER)}${quoteChar}`;
|
|
161
|
-
specs.push(
|
|
306
|
+
specs.push(true
|
|
307
|
+
? { _type: ATTRIBUTE, _name: attrName, _tag: markup.slice(tagNameStart).match(/^[a-zA-Z][^\s/>]*/)?.[0] }
|
|
308
|
+
: { _type: ATTRIBUTE, _name: attrName });
|
|
162
309
|
state = IN_TAG;
|
|
163
310
|
if (quote !== '')
|
|
164
311
|
pos++; // consume the closing quote; unquoted terminators reprocess IN_TAG
|
|
@@ -190,6 +337,14 @@ const scan = (strings) => {
|
|
|
190
337
|
}
|
|
191
338
|
else if (ch === '>') {
|
|
192
339
|
const tagName = markup.slice(tagNameStart).match(/^[a-zA-Z][^\s/>]*/)?.[0] ?? '';
|
|
340
|
+
if (true ) {
|
|
341
|
+
const lower = tagName.toLowerCase();
|
|
342
|
+
const selfClosed = markup.endsWith('/');
|
|
343
|
+
if (lower === 'svg' || lower === 'math')
|
|
344
|
+
foreign += isClosing ? -1 : selfClosed ? 0 : 1;
|
|
345
|
+
else if (foreign < 1)
|
|
346
|
+
warnTagShape(tagName, isClosing, selfClosed);
|
|
347
|
+
}
|
|
193
348
|
if (!isClosing && RAW_TEXT_TAGS.test(tagName) && !markup.endsWith('/')) {
|
|
194
349
|
rawTag = tagName.toLowerCase();
|
|
195
350
|
state = IN_RAW_TEXT;
|
|
@@ -278,6 +433,44 @@ const scan = (strings) => {
|
|
|
278
433
|
* Element-position expression — an element REF, not a no-op. Marked exactly like a bound
|
|
279
434
|
* attribute ('&' cannot begin a real attribute binding), so no new machinery exists for it.
|
|
280
435
|
*/
|
|
436
|
+
if (true && (markup.endsWith('<') || markup.endsWith('</'))) {
|
|
437
|
+
/**
|
|
438
|
+
* Except in **tag position**, where it is a mistake with no useful reading. `<${name}>`
|
|
439
|
+
* lands here because the tag has no name yet, and what the parser then makes of a ref on
|
|
440
|
+
* a nameless element is escaped punctuation. Naming the entry that does support it is
|
|
441
|
+
* more use than an element ref nobody asked for.
|
|
442
|
+
*/
|
|
443
|
+
console.error(`[vera] an expression in tag position (\`<\${…}>\`) is not a dynamic tag name — the ` +
|
|
444
|
+
`template has no element there and the markup around it is rendered as text.\n` +
|
|
445
|
+
`Runtime tag names live in @verajs/renderer/tag:\n\n` +
|
|
446
|
+
` import { html, tag } from '@verajs/renderer/tag';\n` +
|
|
447
|
+
` const heading = tag\`h1\`;\n` +
|
|
448
|
+
` html\`<\${heading}>…</\${heading}>\`\n`);
|
|
449
|
+
}
|
|
450
|
+
/**
|
|
451
|
+
* **And in attribute-*name* position, which is the same mistake one step along.**
|
|
452
|
+
*
|
|
453
|
+
* `<b ${name}="x">`, `<b data-${name}="1">` and `<b a${name}b="1">` all land here: the
|
|
454
|
+
* marker is not preceded by `=`, so it reads as an element ref, and the `="x"` after it
|
|
455
|
+
* stays literal markup. The browser's parser then makes `<b ="x"="">` of it — attributes
|
|
456
|
+
* nobody wrote, silently.
|
|
457
|
+
*
|
|
458
|
+
* **The server already refuses this**, and said so in its README while the client shipped
|
|
459
|
+
* the garbage. A developer rendering only in a browser saw malformed output with no clue,
|
|
460
|
+
* and adding SSR later turned it into a throw with no obvious connection.
|
|
461
|
+
*
|
|
462
|
+
* Told apart from a real element ref by what follows it: a ref is always followed by
|
|
463
|
+
* whitespace, `>` or `/`. Anything else means the marker landed inside a name.
|
|
464
|
+
*/
|
|
465
|
+
const after = strings[i + 1] ?? '';
|
|
466
|
+
if (true && after !== '' && !/^[\s>/]/.test(after)) {
|
|
467
|
+
console.error(`[vera] an expression in attribute-name position (\`<b \${…}="x">\`) is not a dynamic ` +
|
|
468
|
+
`attribute name — a marker is not a name, and the parser makes attributes nobody ` +
|
|
469
|
+
`wrote out of what follows it.\n` +
|
|
470
|
+
`Runtime-named bindings live in @verajs/renderer/spread:\n\n` +
|
|
471
|
+
` import { spread } from '@verajs/renderer/spread';\n` +
|
|
472
|
+
` html\`<b \${spread({ [name]: 'x' })}>…</b>\`\n`);
|
|
473
|
+
}
|
|
281
474
|
markup += ` ${specs.length}${MARKER}="${MARKER}"`;
|
|
282
475
|
specs.push({ _type: ATTRIBUTE, _name: '&' });
|
|
283
476
|
}
|
|
@@ -285,13 +478,92 @@ const scan = (strings) => {
|
|
|
285
478
|
}
|
|
286
479
|
return { markup, specs };
|
|
287
480
|
};
|
|
481
|
+
/**
|
|
482
|
+
* The container of the renderInto call currently committing — how a slot part learns its root
|
|
483
|
+
* (light element vs shadow root) at Instance construction. Commits are synchronous per flush, so
|
|
484
|
+
* one module slot suffices (the `currentInstance` pattern); null outside renderInto (hydration's
|
|
485
|
+
* adoption path constructs elsewhere and the seam stays inert there until it learns adoption).
|
|
486
|
+
*/
|
|
487
|
+
let _slotRoot = null;
|
|
488
|
+
/** See the slotless branch in `Instance`. Once per host tag, so a list cannot flood a console. */
|
|
489
|
+
const warnedSlotless = new Set();
|
|
490
|
+
const warnSlotless = (root) => {
|
|
491
|
+
const tag = root.localName;
|
|
492
|
+
if (warnedSlotless.has(tag))
|
|
493
|
+
return;
|
|
494
|
+
warnedSlotless.add(tag);
|
|
495
|
+
console.warn(`[vera] renderer: <${tag}> renders a \`<slot>\` into LIGHT DOM, but no 'slot' insert is wired — ` +
|
|
496
|
+
`nothing can fill it, so it always shows its fallback, and any content the host is given for ` +
|
|
497
|
+
`it sits beside the component as stray markup instead. Wire it at the app entry, BEFORE anything renders: ` +
|
|
498
|
+
`\`import { slots } from '@verajs/renderer/slots'; wire([renderer, slots])\`. Wiring it later ` +
|
|
499
|
+
`does not help a template that has already rendered — a template resolves this once, at ` +
|
|
500
|
+
`construction, and is interned per call site for the life of the page.`);
|
|
501
|
+
};
|
|
502
|
+
/**
|
|
503
|
+
* `true ` only: the HTML parser dropped an element a binding was written on.
|
|
504
|
+
*
|
|
505
|
+
* Named where it is discovered rather than after the walk, because the SKIP knows exactly which
|
|
506
|
+
* spec went missing — `specs[from]` is the casualty by construction. A post-hoc count can only
|
|
507
|
+
* report the LAST unclaimed spec, which positional pairing makes the wrong element every time, and
|
|
508
|
+
* pointing an author at a tag that rendered correctly is the precise failure this message exists
|
|
509
|
+
* to cure.
|
|
510
|
+
*/
|
|
511
|
+
/**
|
|
512
|
+
* **A child binding directly inside `<table>` renders one shape and PARSES as another.**
|
|
513
|
+
*
|
|
514
|
+
* `<table>${rows}</table>` is conforming HTML — `<tbody>` is omissible — and it is the one place a
|
|
515
|
+
* legal template does not survive a round trip through the platform:
|
|
516
|
+
*
|
|
517
|
+
* - CLIENT RENDER inserts the rows with DOM calls, which apply no parser rules: `table > tr`.
|
|
518
|
+
* - The SAME markup PARSED — a server render the browser re-parses, `innerHTML`, a static file —
|
|
519
|
+
* gets the implied section: `table > tbody > tr`.
|
|
520
|
+
*
|
|
521
|
+
* Measured, both shapes, same template. So a stylesheet written `table > tr` matches on one path
|
|
522
|
+
* and not the other, and hydration discards the server's markup for that container and rebuilds it
|
|
523
|
+
* (*"expected `<tr>` and found `<tbody>`"*) — silently in production, where this call is folded away.
|
|
524
|
+
*
|
|
525
|
+
* **Why this is a warning and not a repair.** Whatever is emitted, the browser re-parses it, and the
|
|
526
|
+
* parser ALWAYS inserts the section — so the only shape all three paths agree on is one where the
|
|
527
|
+
* section is already in the template. The framework could insert it, but that changes the DOM shape
|
|
528
|
+
* of every existing client-rendered table, across the renderer AND `@verajs/ssr`'s serializer, and
|
|
529
|
+
* rests on the SSR shim agreeing with browsers about implied tags. One word from the author reaches
|
|
530
|
+
* the same fixed point with none of that. Owner's call, recorded rather than assumed.
|
|
531
|
+
*
|
|
532
|
+
* Scoped to `<table>` deliberately: `<tbody>` (from rows) and `<colgroup>` (from `<col>`) are the
|
|
533
|
+
* only implied START tags reachable inside a template fragment, and both are children of `<table>`.
|
|
534
|
+
* The omissible END tags — `</li>`, `</p>`, `</td>`, `</option>` and the rest — insert nothing, so
|
|
535
|
+
* they round-trip correctly and are pinned doing so in `tests/dropped-element-bindings.test.mjs`.
|
|
536
|
+
*/
|
|
537
|
+
const warnImplicitSection = (parent) => {
|
|
538
|
+
if (parent?.localName !== 'table')
|
|
539
|
+
return;
|
|
540
|
+
console.warn('[vera] renderer: a binding sits directly inside <table>, where the HTML parser inserts a ' +
|
|
541
|
+
'<tbody> that a client render does not. The same template then renders as `table > tr` and ' +
|
|
542
|
+
'parses as `table > tbody > tr`, so `table > tr` selectors match on only one path and ' +
|
|
543
|
+
'hydration rebuilds this container instead of adopting it. Write the section explicitly — ' +
|
|
544
|
+
'`<table><tbody>${rows}</tbody></table>` — and every path agrees.');
|
|
545
|
+
};
|
|
546
|
+
const warnDroppedBinding = (specs, from, count) => {
|
|
547
|
+
const lost = specs[from];
|
|
548
|
+
const where = lost?._tag
|
|
549
|
+
? `\`${lost._type === ATTRIBUTE ? `${lost._name}=` : ''}\` on <${lost._tag}>`
|
|
550
|
+
: 'a binding';
|
|
551
|
+
console.warn(`[vera] renderer: ${where} never reached the parsed tree — the HTML parser DROPPED the element ` +
|
|
552
|
+
`it was written on, because its parent's content model forbids it (\`<select>\` takes only ` +
|
|
553
|
+
`options, \`<form>\` cannot nest, and so on).\n` +
|
|
554
|
+
`${count} binding(s) lost. The element is gone from the DOM and its binding does nothing; ` +
|
|
555
|
+
`the bindings AFTER it are unaffected, because each marker carries its own index. ` +
|
|
556
|
+
`(Before that they all shifted onto the wrong elements, which is why this kind of mistake ` +
|
|
557
|
+
`used to surface somewhere you had not edited.)\n` +
|
|
558
|
+
`Move the element out of its parent, or use one the parent can hold.`);
|
|
559
|
+
};
|
|
288
560
|
const templateCache = new WeakMap();
|
|
289
561
|
class Template {
|
|
290
562
|
_element;
|
|
291
563
|
_parts = [];
|
|
292
564
|
constructor(result) {
|
|
293
565
|
const type = result._$litType$ ?? 1;
|
|
294
|
-
const { markup, specs } = scan(result.strings);
|
|
566
|
+
const { markup, specs } = scan(result.strings, type);
|
|
295
567
|
this._element = doc.createElement('template');
|
|
296
568
|
/** svg/mathml fragments only parse inside their root; wrap, then unwrap below. */
|
|
297
569
|
this._element.innerHTML = type === 2 ? `<svg>${markup}</svg>` : type === 3 ? `<math>${markup}</math>` : markup;
|
|
@@ -325,6 +597,27 @@ class Template {
|
|
|
325
597
|
if (element.hasAttributes()) {
|
|
326
598
|
for (const attributeName of element.getAttributeNames()) {
|
|
327
599
|
if (attributeName.endsWith(MARKER)) {
|
|
600
|
+
/**
|
|
601
|
+
* **Each marker carries its own spec index in its NAME**, so pairing is addressed
|
|
602
|
+
* rather than positional — and a marker that never arrived is visible the moment the
|
|
603
|
+
* next one does. Both halves matter and neither works alone:
|
|
604
|
+
*
|
|
605
|
+
* - REPAIR: an element the parser drops takes its marker with it. Paired by walk
|
|
606
|
+
* order, that shifted every later binding onto the wrong element, silently —
|
|
607
|
+
* `html\`<select><div title=${'${a}'}>x</div></select><b title=${'${b}'}>\`` rendered
|
|
608
|
+
* `<b title="a">`. Consuming the gap keeps every surviving binding on its own
|
|
609
|
+
* element; only the dropped one is lost.
|
|
610
|
+
* - REPORT: the repair would otherwise SILENCE the problem, which is a correct
|
|
611
|
+
* refusal with nothing to tell the author — so the skip is where the warning lives.
|
|
612
|
+
*/
|
|
613
|
+
const declared = parseInt(attributeName, 10);
|
|
614
|
+
if (declared > specIndex) {
|
|
615
|
+
if (true )
|
|
616
|
+
warnDroppedBinding(specs, specIndex, declared - specIndex);
|
|
617
|
+
do
|
|
618
|
+
parts.push({ _type: IGNORED, _index: -1 });
|
|
619
|
+
while (++specIndex < declared);
|
|
620
|
+
}
|
|
328
621
|
/**
|
|
329
622
|
* The marker attribute's value carries the statics; the REAL (case-preserved) name
|
|
330
623
|
* comes from the spec — the HTML parser lowercases attribute names, which would
|
|
@@ -336,6 +629,15 @@ class Template {
|
|
|
336
629
|
_index: -1,
|
|
337
630
|
_name: spec._name,
|
|
338
631
|
_statics: element.getAttribute(attributeName).split(MARKER),
|
|
632
|
+
/**
|
|
633
|
+
* Computed here — once per template, ever — so the first commit of a nullish
|
|
634
|
+
* binding knows whether a fresh clone even carries the attribute. It usually does
|
|
635
|
+
* not, and the unconditional removal this feeds cost a real DOM call per element
|
|
636
|
+
* per create: 1,000 no-op `removeAttribute`s on the 1,000-row benchmark. The one
|
|
637
|
+
* case that must still remove — `<b title="a" title=${null}>`, where the parser
|
|
638
|
+
* keeps the first duplicate — is exactly what this reads.
|
|
639
|
+
*/
|
|
640
|
+
_present: element.hasAttribute(spec._name),
|
|
339
641
|
_node: element,
|
|
340
642
|
});
|
|
341
643
|
element.removeAttribute(attributeName);
|
|
@@ -367,10 +669,41 @@ class Template {
|
|
|
367
669
|
/** Re-aim the walker before removing the node it stands on. */
|
|
368
670
|
markerWalker.currentNode = primedText;
|
|
369
671
|
node.remove();
|
|
672
|
+
if (true )
|
|
673
|
+
warnImplicitSection(primedText.parentNode);
|
|
370
674
|
parts.push({ _type: CHILD, _index: -1, _node: primedText });
|
|
371
675
|
consumeIgnored();
|
|
372
676
|
}
|
|
373
677
|
}
|
|
678
|
+
/**
|
|
679
|
+
* **CONSERVATION OF MARKERS — the walk must claim every spec the scan emitted.**
|
|
680
|
+
*
|
|
681
|
+
* The loop above pairs specs with markers in document order. If the HTML parser DROPPED the
|
|
682
|
+
* element a binding was written on, that marker never exists, the loop runs out of nodes early,
|
|
683
|
+
* and `specIndex` stops short — and because pairing is POSITIONAL, every binding after the
|
|
684
|
+
* missing one has already been handed the value of its predecessor. Measured:
|
|
685
|
+
*
|
|
686
|
+
* html`<select><div title=${a}>x</div></select><b title=${b}>after</b>`
|
|
687
|
+
*
|
|
688
|
+
* renders `<b title="a">` — the value written for the `<div>`, on an unrelated element, with
|
|
689
|
+
* no error anywhere. `<form>` inside `<form>` does the same. HTML's parser drops elements its
|
|
690
|
+
* content model forbids, which is correct of it and invisible to everything else here.
|
|
691
|
+
*
|
|
692
|
+
* **This is deliberately not a content-model check.** A table of what may contain what is a
|
|
693
|
+
* closed vocabulary over an open space: it catches what somebody enumerated, needs maintenance
|
|
694
|
+
* as HTML evolves, and would cover the compiler only — while this counts what actually
|
|
695
|
+
* happened, in JSX and hand-written templates alike, for every dropping context including the
|
|
696
|
+
* ones nobody listed. The cost of knowing is one integer comparison the construction already
|
|
697
|
+
* had lying around.
|
|
698
|
+
*
|
|
699
|
+
* The gap it cannot close, named rather than implied: a dropped element carrying NO bindings
|
|
700
|
+
* loses nothing to count. That is harmless to the renderer — nothing shifts — and it is the
|
|
701
|
+
* restructuring class, which `tests/jsx-tree-parity.test.mjs` records instead.
|
|
702
|
+
*/
|
|
703
|
+
if (true && specIndex < specs.length) {
|
|
704
|
+
/** A casualty at the very END has no later marker to reveal it, so the tail is checked too. */
|
|
705
|
+
warnDroppedBinding(specs, specIndex, specs.length - specIndex);
|
|
706
|
+
}
|
|
374
707
|
/** Pass 2 — INDEX over ELEMENT | TEXT, the mask instances walk with. */
|
|
375
708
|
instanceWalker.currentNode = content;
|
|
376
709
|
let nodeIndex = -1;
|
|
@@ -388,6 +721,40 @@ class Template {
|
|
|
388
721
|
}
|
|
389
722
|
for (const part of parts)
|
|
390
723
|
part._node = undefined;
|
|
724
|
+
/**
|
|
725
|
+
* THE SLOT WALK — the whole template-side seam, and it runs only when a 'slot' insert is
|
|
726
|
+
* wired at construction. One dedicated pass discovers `<slot>` elements AND indexes them in
|
|
727
|
+
* the same ELEMENT|TEXT numbering the instance walk uses (Text has no localName, so no
|
|
728
|
+
* nodeType check is needed). Passes 1 and 2 above are byte-identical to their pre-seam
|
|
729
|
+
* selves: an unwired app's construction path is untouched, and its only cost is this one
|
|
730
|
+
* registry lookup per template construction.
|
|
731
|
+
*
|
|
732
|
+
* **Resolved per TEMPLATE, and templates are cached per call site for the life of the page** —
|
|
733
|
+
* so a shape first constructed before `wire([slots])` ran never gains slot support, silently.
|
|
734
|
+
* That is the ordinary insert contract (wire at the app entry, beside the renderer, before
|
|
735
|
+
* anything renders) and it is stated in the slots module's own docs; resolving per INSTANCE
|
|
736
|
+
* instead would move a registry lookup onto the hot path for every app, which is the trade
|
|
737
|
+
* this design refuses.
|
|
738
|
+
*/
|
|
739
|
+
const seam = slotSeam();
|
|
740
|
+
/**
|
|
741
|
+
* **Dev-only: remember that this markup HAS slots even when nothing can distribute them.**
|
|
742
|
+
* Without it the two ways of getting the wiring wrong are indistinguishable from a component
|
|
743
|
+
* that simply has no slots — see the warning at the instance's slot mount.
|
|
744
|
+
*/
|
|
745
|
+
if (true && seam === undefined && markup.includes('<slot'))
|
|
746
|
+
this._slotless = true;
|
|
747
|
+
if (seam !== undefined) {
|
|
748
|
+
instanceWalker.currentNode = content;
|
|
749
|
+
let index = -1;
|
|
750
|
+
while ((node = instanceWalker.nextNode()) !== null) {
|
|
751
|
+
index++;
|
|
752
|
+
if (node.localName === 'slot') {
|
|
753
|
+
this._seam = seam;
|
|
754
|
+
(this._slots ??= []).push(index);
|
|
755
|
+
}
|
|
756
|
+
}
|
|
757
|
+
}
|
|
391
758
|
}
|
|
392
759
|
}
|
|
393
760
|
const getTemplate = (result) => {
|
|
@@ -399,8 +766,6 @@ const getTemplate = (result) => {
|
|
|
399
766
|
const IGNORED_PART = { _commit: (_values, index) => index + 1 };
|
|
400
767
|
/** Never equal to any user value, so the first commit always runs. */
|
|
401
768
|
const UNSET = {};
|
|
402
|
-
/** Removal target: nodes moved here are dropped when it is emptied. */
|
|
403
|
-
const SCRATCH = doc.createDocumentFragment();
|
|
404
769
|
/** A fresh markered part: two comments inserted before `ref` in `parent`. */
|
|
405
770
|
const createMarkeredPart = (parent, ref) => {
|
|
406
771
|
const start = comment();
|
|
@@ -409,13 +774,195 @@ const createMarkeredPart = (parent, ref) => {
|
|
|
409
774
|
parent.insertBefore(end, ref);
|
|
410
775
|
return new ChildPart(start, end);
|
|
411
776
|
};
|
|
412
|
-
|
|
777
|
+
/**
|
|
778
|
+
* Text for an attribute built from several expressions.
|
|
779
|
+
*
|
|
780
|
+
* `` `${value}` `` rather than `String(value)`, and the difference is exactly one case. Both are
|
|
781
|
+
* ToString with hint `'string'` for everything else; `String` alone special-cases a **symbol** and
|
|
782
|
+
* returns its description instead of throwing. Every single-expression binding assigns straight to
|
|
783
|
+
* the DOM and gets WebIDL's `DOMString` conversion, which throws on one — so `title=${symbol}` threw
|
|
784
|
+
* and `title="a ${symbol} b"` quietly rendered `a Symbol(s) b`. The same sigil on the same attribute,
|
|
785
|
+
* disagreeing with itself depending on whether static text sat beside it.
|
|
786
|
+
*/
|
|
787
|
+
const toText = (value) => (value == null ? '' : `${value}`);
|
|
413
788
|
/** Binding kinds, resolved once from the attribute name's first character. */
|
|
414
789
|
const ATTR = 0; // plain attribute
|
|
415
790
|
const PROPERTY = 1; // .name
|
|
416
791
|
const BOOLEAN = 2; // ?name
|
|
417
|
-
|
|
418
|
-
|
|
792
|
+
/**
|
|
793
|
+
* `!name` — a property written from the *live* DOM rather than from what this binding last wrote.
|
|
794
|
+
*
|
|
795
|
+
* Numbered below `EVENT` deliberately: `kind >= EVENT` is what decides a value is passed raw rather
|
|
796
|
+
* than joined from the statics, and a live binding is a property, so `!title="a${x}b"` has to join
|
|
797
|
+
* like every other one.
|
|
798
|
+
*/
|
|
799
|
+
const LIVE = 3;
|
|
800
|
+
const EVENT = 4; // @name
|
|
801
|
+
/** A binding that must never write — see the `__proto__` refusal in the constructor. */
|
|
802
|
+
const REFUSED = -1;
|
|
803
|
+
/** `.name` on a custom element nothing receives yet — records into `_$props$`, then becomes
|
|
804
|
+
* `PROPERTY`. A distinct kind keeps the steady-state property path free of any adoption check. */
|
|
805
|
+
const PROP_ADOPT = 6;
|
|
806
|
+
/**
|
|
807
|
+
* The `PROP_ADOPT` commit, kept OUT of `_commit` so that function's size — and the JIT layout of
|
|
808
|
+
* its hot `PROPERTY`/`ATTR` branches — is unchanged from before this feature. `_commit` carries one
|
|
809
|
+
* dispatch line; all of this lives here, off every part's steady state.
|
|
810
|
+
*
|
|
811
|
+
* One question decides everything: **after the write, does anything receive this property?** An
|
|
812
|
+
* accessor anywhere on the chain — the platform's own (`title`, `hidden`), a component's declared
|
|
813
|
+
* one, or the pair core's `init()` defines — means the write just landed in real hands: no record,
|
|
814
|
+
* and the part rejoins `PROPERTY` for good. The walk is one step when the write created an own data
|
|
815
|
+
* property (nobody consumed it) and stops at the first descriptor either way, and it is what keeps
|
|
816
|
+
* a platform property on a lazy tag out of the record — recording `.title` would end with the drain
|
|
817
|
+
* shadowing `HTMLElement.prototype.title` and breaking it.
|
|
818
|
+
*
|
|
819
|
+
* An unreceived write is recorded under the sigiled expando **`_$props$`**, because two arrival
|
|
820
|
+
* orders both need it: on a LAZY tag the value sits as a plain own property that the class's field
|
|
821
|
+
* initializers will overwrite at upgrade (the clobber the `PROPERTY` branch only *detects*), and on
|
|
822
|
+
* an EAGER one the value survives but is indistinguishable from the component's own fields by the
|
|
823
|
+
* time `init()` runs. The record answers both — core's `init()` drains it, re-applying values
|
|
824
|
+
* unconditionally, which repairs BOTH spellings of the clobber (`item;` and `item = default`): it
|
|
825
|
+
* never asks whether a clobber happened, it asserts a bound value outranks a class default, which
|
|
826
|
+
* is what props mean. Element-carried because `./spread.ts` writes the same properties from a
|
|
827
|
+
* separate bundle with no shared registry — the `_$`-sigiled member is the cross-bundle channel,
|
|
828
|
+
* and the recorder there is this one's deliberate twin.
|
|
829
|
+
*
|
|
830
|
+
* Returns the part's NEXT kind: `PROPERTY` once something receives the property or the element is
|
|
831
|
+
* upgraded (its record is final — `init()` drains it in the same tick) or has no realm; `REFUSED`
|
|
832
|
+
* for a getter with no setter, so the binding goes inert instead of the flipped plain write
|
|
833
|
+
* throwing on the next commit; `0` to stay adopting — a dash-named element that never upgrades and
|
|
834
|
+
* never receives keeps recording, so its record stays current rather than staling. The one
|
|
835
|
+
* retention this leaves: a defined non-vera element with a plain data property keeps its FIRST
|
|
836
|
+
* committed values in `_$props$` for its lifetime — bounded, one generation, and the part itself
|
|
837
|
+
* already retains the current generation in `_committed`.
|
|
838
|
+
*/
|
|
839
|
+
const commitAdopt = (element, name, value) => {
|
|
840
|
+
const el = element;
|
|
841
|
+
/**
|
|
842
|
+
* The walk comes BEFORE the write, because what the walk finds decides whether writing is even
|
|
843
|
+
* legal: a SETTER receives the value (and a setter that throws is the component's own error), a
|
|
844
|
+
* GETTER with no setter cannot — the old order assigned first, which in strict mode threw a raw
|
|
845
|
+
* TypeError out of the render for the eager spelling of exactly the case the drain refuses by
|
|
846
|
+
* name for the lazy one. Same contested state, one rule, both arrival orders — and the server's
|
|
847
|
+
* `deliverProperty` applies it too. The dev warning defers to `_$adopt$` where it exists: an
|
|
848
|
+
* initialized component's drain already speaks, and two voices for one binding is noise.
|
|
849
|
+
*/
|
|
850
|
+
let carrier = el;
|
|
851
|
+
while (carrier !== null) {
|
|
852
|
+
const desc = Object.getOwnPropertyDescriptor(carrier, name);
|
|
853
|
+
if (desc !== undefined) {
|
|
854
|
+
if (desc.set !== undefined) {
|
|
855
|
+
el[name] = value;
|
|
856
|
+
return PROPERTY;
|
|
857
|
+
}
|
|
858
|
+
if (desc.get !== undefined) {
|
|
859
|
+
/** An initialized component's receiver owns the refusal (and its channel); for anything
|
|
860
|
+
* else this is the only door, so it says so itself. Either way the binding goes INERT —
|
|
861
|
+
* flipping to `PROPERTY` would make the next commit's plain write throw. */
|
|
862
|
+
if (el._$adopt$ !== undefined)
|
|
863
|
+
el._$adopt$(name, value);
|
|
864
|
+
else if (true )
|
|
865
|
+
console.warn(`[vera] renderer: <${element.localName}> declares \`${name}\` as a getter with no ` +
|
|
866
|
+
`setter — the value bound by \`.${name}=\${…}\` cannot be delivered and the binding ` +
|
|
867
|
+
`is ignored. Add a setter, or stop binding it.`);
|
|
868
|
+
return REFUSED;
|
|
869
|
+
}
|
|
870
|
+
break; // a data property — an own field, or an inherited default: nothing receives it
|
|
871
|
+
}
|
|
872
|
+
carrier = Object.getPrototypeOf(carrier);
|
|
873
|
+
}
|
|
874
|
+
el[name] = value;
|
|
875
|
+
/**
|
|
876
|
+
* An initialized component receives LIVE: `init()` left `_$adopt$` on the element, and a key it
|
|
877
|
+
* has not adopted yet goes through that door — a record here would never be read again, because
|
|
878
|
+
* the drain already ran. This is how a hydrated child gets the props its parent commits after
|
|
879
|
+
* the child settled, and how a spread bag's conditional key arrives reactive on a live element.
|
|
880
|
+
*/
|
|
881
|
+
if (el._$adopt$ !== undefined) {
|
|
882
|
+
el._$adopt$(name, value);
|
|
883
|
+
return PROPERTY;
|
|
884
|
+
}
|
|
885
|
+
const record = (el._$props$ ??= {});
|
|
886
|
+
const firstRecording = !Object.hasOwn(record, name);
|
|
887
|
+
record[name] = value;
|
|
888
|
+
/**
|
|
889
|
+
* Upgrade is read off the PROTOTYPE, never off `el.constructor`: a spread bag's keys are runtime
|
|
890
|
+
* data, so a bag carrying a key named `constructor` writes an own property that shadows the real
|
|
891
|
+
* one, and a check that reads it would then misjudge every later commit. No property write can
|
|
892
|
+
* move an element's prototype — the one assignment that could, `__proto__`, both twins refuse.
|
|
893
|
+
* The realm comes from the element, as always.
|
|
894
|
+
*/
|
|
895
|
+
const win = element.ownerDocument.defaultView;
|
|
896
|
+
const upgraded = win === null || Object.getPrototypeOf(el) !== win.HTMLElement.prototype;
|
|
897
|
+
/**
|
|
898
|
+
* **The clobber detector, for the element the drain will never reach.** A component that calls
|
|
899
|
+
* `init()` has the record re-applied, so for it the pre-upgrade window is repaired; an element
|
|
900
|
+
* that never drains — a plain custom element with a class field — still loses the bound value to
|
|
901
|
+
* the field initializer at upgrade, exactly as before this feature, and still deserves the
|
|
902
|
+
* warning. Told apart by OWNERSHIP, not by value: after the definition arrives (and, for a
|
|
903
|
+
* connected element, `connectedCallback` and the drain have run synchronously inside `define()`),
|
|
904
|
+
* an own accessor means the drain took the property and there is nothing to report. Identity
|
|
905
|
+
* against the COMMITTED value would lie twice — a drained value reads back through the store's
|
|
906
|
+
* proxy, and a value superseded by a later pre-upgrade commit differs without anything being
|
|
907
|
+
* wrong — so the comparison is against the RECORD, which later recordings keep current, and the
|
|
908
|
+
* subscription is installed once per (element, property), on the first recording. The registry
|
|
909
|
+
* is the element's own realm's. Development only; production carries no check, no message, no
|
|
910
|
+
* `whenDefined` subscription.
|
|
911
|
+
*/
|
|
912
|
+
if (true && win !== null && !upgraded && firstRecording) {
|
|
913
|
+
const tag = element.localName;
|
|
914
|
+
win.customElements.whenDefined(tag).then(() => {
|
|
915
|
+
/** Ownership is asked of the whole CHAIN: the drain's own accessor, a class's prototype
|
|
916
|
+
* pair the value was handed to, or a get-only surface the drain refused by name — every
|
|
917
|
+
* one means the property has an owner and this closure has nothing left to report. */
|
|
918
|
+
let carrier = el;
|
|
919
|
+
let owned = false;
|
|
920
|
+
while (carrier !== null) {
|
|
921
|
+
const desc = Object.getOwnPropertyDescriptor(carrier, name);
|
|
922
|
+
if (desc !== undefined) {
|
|
923
|
+
owned = desc.get !== undefined || desc.set !== undefined;
|
|
924
|
+
break;
|
|
925
|
+
}
|
|
926
|
+
carrier = Object.getPrototypeOf(carrier);
|
|
927
|
+
}
|
|
928
|
+
if (!owned && el[name] !== record[name])
|
|
929
|
+
console.warn(`[vera] renderer: the value bound by \`.${name}=\${…}\` on <${tag}> was replaced ` +
|
|
930
|
+
`while the element upgraded. A class field is the usual cause: at ES2022 ` +
|
|
931
|
+
`\`${name}?: …\` emits \`${name};\`, which runs during upgrade and overwrites ` +
|
|
932
|
+
`whatever was set beforehand — write it \`declare ${name}?: …\` instead, which ` +
|
|
933
|
+
`emits nothing. A component that calls init() adopts bound properties automatically ` +
|
|
934
|
+
`and never sees this; this element did not. Ignore this if the component replaced ` +
|
|
935
|
+
`the value on purpose.`);
|
|
936
|
+
});
|
|
937
|
+
}
|
|
938
|
+
return upgraded ? PROPERTY : 0;
|
|
939
|
+
};
|
|
940
|
+
/**
|
|
941
|
+
* Calls an element ref, and survives one that throws.
|
|
942
|
+
*
|
|
943
|
+
* A ref runs in the middle of committing a template's parts, so an unguarded throw left the commit
|
|
944
|
+
* half applied and unwound the render that triggered it — the component's shadow root ended up
|
|
945
|
+
* **empty and stayed that way**, and every later update threw at the same line. The error was
|
|
946
|
+
* reported, so the only symptom was a component that had silently stopped existing.
|
|
947
|
+
*
|
|
948
|
+
* The same judgement `handleEvent` makes a few lines up: a mistake in code the template was handed
|
|
949
|
+
* is named, not raised from inside the framework at a point where the value's origin is long gone.
|
|
950
|
+
* The prefix goes on our own sentence and the error is passed alongside, so it stays filterable
|
|
951
|
+
* without misattributing someone else's `Error`.
|
|
952
|
+
*/
|
|
953
|
+
const applyRef = (callback, element) => {
|
|
954
|
+
try {
|
|
955
|
+
callback(element);
|
|
956
|
+
}
|
|
957
|
+
catch (error) {
|
|
958
|
+
/** The sentence is development's; production keeps the prefix and the error carries the rest. */
|
|
959
|
+
if (true )
|
|
960
|
+
console.error('[vera] an element ref threw; the render continued without it.', error);
|
|
961
|
+
else
|
|
962
|
+
console.error('[vera] ref threw', error);
|
|
963
|
+
}
|
|
964
|
+
};
|
|
965
|
+
const REF = 5; // element-position expression
|
|
419
966
|
class AttrPart {
|
|
420
967
|
_element;
|
|
421
968
|
_name;
|
|
@@ -425,15 +972,52 @@ class AttrPart {
|
|
|
425
972
|
_isFullValue; // exactly one expression with no static text around it
|
|
426
973
|
_committed = UNSET;
|
|
427
974
|
_handler = null;
|
|
428
|
-
|
|
975
|
+
/** `<select>.value`, which cannot be applied where it is written — see `pendingSelects`. */
|
|
976
|
+
_select = false;
|
|
977
|
+
/** The template statically wrote this attribute, so a first nullish commit must still remove. */
|
|
978
|
+
_present;
|
|
979
|
+
constructor(element, name, statics, present = false) {
|
|
429
980
|
const first = name[0];
|
|
430
|
-
let kind = first === '.'
|
|
981
|
+
let kind = first === '.'
|
|
982
|
+
? PROPERTY
|
|
983
|
+
: first === '?'
|
|
984
|
+
? BOOLEAN
|
|
985
|
+
: first === '@'
|
|
986
|
+
? EVENT
|
|
987
|
+
: first === '&'
|
|
988
|
+
? REF
|
|
989
|
+
: first === '!'
|
|
990
|
+
? LIVE
|
|
991
|
+
: ATTR;
|
|
431
992
|
let realName = kind ? name.slice(1) : name;
|
|
993
|
+
/**
|
|
994
|
+
* **`__proto__` is not a property write, so no property binding may make one.**
|
|
995
|
+
*
|
|
996
|
+
* `element.__proto__ = value` hits `Object.prototype`'s `__proto__` ACCESSOR and replaces the
|
|
997
|
+
* element's prototype, stripping every DOM method it has. `.__proto__=${x}` crashed out of the
|
|
998
|
+
* commit with an unreadable internal error; `!__proto__=${x}` bricked the element silently and
|
|
999
|
+
* the wreckage surfaced in a LATER render, naming the renderer rather than the binding. There
|
|
1000
|
+
* is no legitimate use, so unlike `.innerHTML` there is no spelling to point at — the binding
|
|
1001
|
+
* is refused and never writes.
|
|
1002
|
+
*
|
|
1003
|
+
* **The deliberate twin of `refusedSink` in `./spread.ts`**, which refuses the same name for
|
|
1004
|
+
* the same reason. The two entries are independent bundles and neither imports the other, so
|
|
1005
|
+
* the rule is copied on purpose (the repo's standing note: sigil rules live in both AttrPart
|
|
1006
|
+
* and spread, and a fix has to visit every copy). `tests/dangerous-binding-matrix.test.mjs`
|
|
1007
|
+
* fails if one of them starts refusing something the other allows.
|
|
1008
|
+
*/
|
|
1009
|
+
if ((kind === PROPERTY || kind === LIVE) && realName === '__proto__') {
|
|
1010
|
+
kind = REFUSED;
|
|
1011
|
+
if (true )
|
|
1012
|
+
console.warn(`[vera] <${element.localName}> binds \`${name}\`, which would replace the element's own ` +
|
|
1013
|
+
`prototype and destroy it — no property write does this, and no use of it is legitimate. ` +
|
|
1014
|
+
`The binding is ignored.`);
|
|
1015
|
+
}
|
|
432
1016
|
/**
|
|
433
1017
|
* React muscle-memory, buildless: `onClick=${fn}` ≡ `@click=${fn}`. Strictly `on` + a capital —
|
|
434
1018
|
* all-lowercase `onclick` stays a plain attribute (legal inline-handler HTML).
|
|
435
1019
|
*
|
|
436
|
-
* `@verajs/spread` repeats these rules rather than importing them. Sharing them through
|
|
1020
|
+
* `@verajs/renderer/spread` repeats these rules rather than importing them. Sharing them through
|
|
437
1021
|
* `@verajs/shared-utils` was tried and reverted: the shared form has to return both the kind and
|
|
438
1022
|
* the name, and the tuple it allocates cost this bundle 10 B. Principle #5 allows deliberate
|
|
439
1023
|
* duplication where two things can legitimately diverge; here #7 decides it — weight is the
|
|
@@ -443,20 +1027,103 @@ class AttrPart {
|
|
|
443
1027
|
kind = EVENT;
|
|
444
1028
|
realName = name.slice(2).toLowerCase();
|
|
445
1029
|
}
|
|
1030
|
+
/**
|
|
1031
|
+
* **A property write to a custom element starts as `PROP_ADOPT`**, a distinct kind so the
|
|
1032
|
+
* steady-state `PROPERTY` commit path stays byte-for-byte unchanged — zero added instruction
|
|
1033
|
+
* for every `.value=` on a built-in. Every dash-named element starts here, defined or not,
|
|
1034
|
+
* because the record has to exist for BOTH arrival orders: an eager component's first commit
|
|
1035
|
+
* lands after upgrade but before `init()` (one commit records, then the part flips), and a
|
|
1036
|
+
* lazy one's land before upgrade (the part records until the definition arrives). `commitAdopt`
|
|
1037
|
+
* decides which per commit and flips the part back to `PROPERTY` the moment something real
|
|
1038
|
+
* receives the property, so the window is one commit for a defined element and the pre-upgrade
|
|
1039
|
+
* stretch for a lazy one.
|
|
1040
|
+
*/
|
|
1041
|
+
if (kind === PROPERTY && element.localName.includes('-'))
|
|
1042
|
+
kind = PROP_ADOPT;
|
|
446
1043
|
this._kind = kind;
|
|
447
1044
|
this._name = realName;
|
|
448
1045
|
this._element = element;
|
|
449
1046
|
this._statics = statics;
|
|
450
1047
|
this._slots = statics.length - 1;
|
|
451
1048
|
this._isFullValue = this._slots === 1 && statics[0] === '' && statics[1] === '';
|
|
1049
|
+
/** Resolved once, here, so the commit path costs one boolean rather than two comparisons. */
|
|
1050
|
+
this._select = kind === PROPERTY && realName === 'value' && element.localName === 'select';
|
|
1051
|
+
this._present = present;
|
|
452
1052
|
}
|
|
453
|
-
/**
|
|
1053
|
+
/**
|
|
1054
|
+
* Releases an element ref, because the element it named is going away.
|
|
1055
|
+
*
|
|
1056
|
+
* A ref was told about attachment and never about detachment, so it kept a detached node alive and
|
|
1057
|
+
* a component reading `myRef.value` after a subtree was replaced got the old element back. Lit
|
|
1058
|
+
* passes `undefined` for the same reason.
|
|
1059
|
+
*
|
|
1060
|
+
* `null` rather than `undefined`, because `.value` is a store property and `null` reads as
|
|
1061
|
+
* "deliberately nothing" where `undefined` reads as "never set".
|
|
1062
|
+
*
|
|
1063
|
+
* **Reached when a subtree is rendered away, and deliberately not when a component is removed
|
|
1064
|
+
* from the document.** The two are the same event to a reader and not to this renderer: a
|
|
1065
|
+
* disconnect here is not a destruction, since moving a node between parents fires one and the
|
|
1066
|
+
* component renders again on reconnect. Releasing there would blank every ref for the frame a
|
|
1067
|
+
* move takes, and `_committed = UNSET` below means the re-apply could only happen on the next
|
|
1068
|
+
* pass. Measured in `tests/renderer-ref-lifetime.test.mjs`, which asserts both halves so the
|
|
1069
|
+
* asymmetry is a decision rather than something nobody looked at.
|
|
1070
|
+
*
|
|
1071
|
+
* A **self-applying** value is
|
|
1072
|
+
* skipped: `_$apply$` receives the part and owns its own lifecycle, so telling it about detachment
|
|
1073
|
+
* here would be a second protocol contradicting the first.
|
|
1074
|
+
*/
|
|
1075
|
+
_release() {
|
|
1076
|
+
const value = this._committed;
|
|
1077
|
+
if (typeof value === 'function')
|
|
1078
|
+
applyRef(value, null);
|
|
1079
|
+
else if (value !== null && typeof value === 'object' && value._$apply$ === undefined)
|
|
1080
|
+
value.value = null;
|
|
1081
|
+
this._committed = UNSET;
|
|
1082
|
+
}
|
|
1083
|
+
/**
|
|
1084
|
+
* Stable listener; swapping one function for another never touches the DOM.
|
|
1085
|
+
*
|
|
1086
|
+
* **It is not registered exactly once, and the difference is load-bearing.** A handler set back to
|
|
1087
|
+
* `undefined` or `false` nulls `_handler` *without removing the listener* — inert, because
|
|
1088
|
+
* `handleEvent` finds nothing callable — so the next non-null value sees `_handler === null` and
|
|
1089
|
+
* calls `addEventListener` again. Measured: `function -> undefined -> function` registers twice.
|
|
1090
|
+
*
|
|
1091
|
+
* That is harmless only because the listener passed is **`this`, the part object itself**. The
|
|
1092
|
+
* platform ignores a repeated `(type, listener, capture)` triple, verified with no framework
|
|
1093
|
+
* involved — the same listener object added three times fires once. Pass a fresh closure here
|
|
1094
|
+
* instead and dedup stops applying: every toggle through null adds another live listener, silently,
|
|
1095
|
+
* and only in components that turn a handler off and on again.
|
|
1096
|
+
*
|
|
1097
|
+
* `tests/event-binding-fuzz.test.mjs` holds that as an invariant — it counts *fires*, not
|
|
1098
|
+
* `addEventListener` calls, and making this listener a closure fails it.
|
|
1099
|
+
*
|
|
1100
|
+
* **Two shapes, because `addEventListener` takes two.** A function is called with the element as
|
|
1101
|
+
* `this`; an object with a `handleEvent` method is invoked through it — the platform's own
|
|
1102
|
+
* `EventListenerObject` protocol, which every engine accepts and lit supports. This used to call
|
|
1103
|
+
* `.call()` unconditionally, so passing the platform's own listener shape bound successfully and
|
|
1104
|
+
* then threw `this._handler.call is not a function` on **every** dispatch.
|
|
1105
|
+
*
|
|
1106
|
+
* Anything else is inert rather than throwing. A truthy non-function is a mistake, and
|
|
1107
|
+
* development names it at the binding (see the `EVENT` branch in `_commit`) — where the mistake
|
|
1108
|
+
* still is. Throwing here instead would raise from inside the framework on every user click, at a
|
|
1109
|
+
* point where the value's origin is long gone.
|
|
1110
|
+
*/
|
|
454
1111
|
handleEvent(event) {
|
|
455
|
-
|
|
456
|
-
|
|
1112
|
+
const handler = this._handler;
|
|
1113
|
+
if (typeof handler === 'function')
|
|
1114
|
+
handler.call(this._element, event);
|
|
1115
|
+
else if (typeof handler?.handleEvent === 'function')
|
|
1116
|
+
handler.handleEvent(event);
|
|
457
1117
|
}
|
|
458
|
-
|
|
1118
|
+
/**
|
|
1119
|
+
* `adopting` is set only by `@verajs/renderer/hydrate`, and only changes what happens to the
|
|
1120
|
+
* three form-value properties the server can express in markup — see the branch below.
|
|
1121
|
+
*/
|
|
1122
|
+
_commit(values, index, adopting) {
|
|
459
1123
|
const kind = this._kind;
|
|
1124
|
+
/** Refused in the constructor and never writes — it still has to consume its slots. */
|
|
1125
|
+
if (kind === REFUSED)
|
|
1126
|
+
return index + this._slots;
|
|
460
1127
|
let value;
|
|
461
1128
|
if (this._isFullValue || kind >= EVENT) {
|
|
462
1129
|
value = values[index]; // raw and uncoerced — events and refs receive the actual value
|
|
@@ -468,85 +1135,175 @@ class AttrPart {
|
|
|
468
1135
|
joined += toText(values[index + i]) + statics[i + 1];
|
|
469
1136
|
value = joined;
|
|
470
1137
|
}
|
|
471
|
-
|
|
472
|
-
|
|
473
|
-
|
|
1138
|
+
/**
|
|
1139
|
+
* **A live property asks the element, not its own memory.**
|
|
1140
|
+
*
|
|
1141
|
+
* Every other kind skips a write when the value matches what it last wrote. That is what keeps
|
|
1142
|
+
* a field someone has typed into — and it is wrong for a control whose DOM state changes as a
|
|
1143
|
+
* *side effect of interacting with a sibling*. Clicking one radio unchecks the others with no
|
|
1144
|
+
* event on them, so their bindings still say `true`, still match `_committed`, and never write
|
|
1145
|
+
* again: the model and the page diverge and no amount of re-rendering reconciles them. A
|
|
1146
|
+
* `<select>`'s options are the same shape.
|
|
1147
|
+
*
|
|
1148
|
+
* Deliberately narrow. This is not for text inputs — bind those with `.value` and let a
|
|
1149
|
+
* person's typing stand. `?hidden` and plain attributes are not offered either: nothing changes
|
|
1150
|
+
* them behind the renderer's back, so there is nothing to re-read.
|
|
1151
|
+
*/
|
|
1152
|
+
if (kind === LIVE) {
|
|
1153
|
+
this._committed = value;
|
|
1154
|
+
/**
|
|
1155
|
+
* **Except while adopting — on a form control.** Hydration reaches a DOM a person may
|
|
1156
|
+
* already have used, and the click that checked a radio happened before any handler existed
|
|
1157
|
+
* to tell the store about it — so re-asserting the server's choice here would throw the
|
|
1158
|
+
* interaction away and nothing would ever put it back. Recorded, not written, exactly as
|
|
1159
|
+
* the other form properties are; the first state-driven render after that applies live
|
|
1160
|
+
* semantics normally.
|
|
1161
|
+
*
|
|
1162
|
+
* **A COMPONENT tag is the exception to the exception**: there is no user-editable carrier
|
|
1163
|
+
* behind `!prop` on a component — it is a property delivery spelled with `!` — and the
|
|
1164
|
+
* server DELIVERED it to the child's render, so yielding here dropped the one copy the
|
|
1165
|
+
* client would ever get and hydration regressed the child's content to its prop-less state.
|
|
1166
|
+
* Found by the hydration fixture on its first run. The write is unconditional and routes
|
|
1167
|
+
* through the element like any component prop: an accessor receives it, an initialized
|
|
1168
|
+
* component adopts it live.
|
|
1169
|
+
*/
|
|
1170
|
+
if (false && adopting) {
|
|
1171
|
+
/** Routed through `commitAdopt`, not written raw: the child hydrated BEFORE this commit,
|
|
1172
|
+
* so only the adoption door re-runs its render. The part stays `LIVE` — the return is
|
|
1173
|
+
* deliberately dropped — so live semantics resume on the next state-driven render. */
|
|
1174
|
+
if (this._element.localName.includes('-'))
|
|
1175
|
+
commitAdopt(this._element, this._name, value);
|
|
1176
|
+
}
|
|
1177
|
+
else {
|
|
1178
|
+
const liveTarget = this._element;
|
|
1179
|
+
if (liveTarget[this._name] !== value)
|
|
1180
|
+
liveTarget[this._name] = value;
|
|
1181
|
+
}
|
|
1182
|
+
return index + this._slots;
|
|
1183
|
+
}
|
|
1184
|
+
/**
|
|
1185
|
+
* **A `<select>`'s value cannot be applied where it is written.**
|
|
1186
|
+
*
|
|
1187
|
+
* Assigning it selects an option, and at the moment this part commits the options may not exist:
|
|
1188
|
+
* parts commit in document order, so a nested `${items.map(…)}` has not run, and an `<option
|
|
1189
|
+
* value=${id}>` has not been given its value either. The assignment then matches nothing, and the
|
|
1190
|
+
* select falls back to its first option — silently showing the wrong one. Measured: a nested list
|
|
1191
|
+
* selected index 0 instead of 1, and dynamic option values selected nothing at all.
|
|
1192
|
+
* **lit-html has the same defect, byte for byte** — it was measured there too. React solves it by
|
|
1193
|
+
* special-casing `<select value>` and applying it after children mount, which is what this is.
|
|
1194
|
+
*
|
|
1195
|
+
* Queued rather than dirty-checked, and that is deliberate: the value can be unchanged while the
|
|
1196
|
+
* *options* are replaced, which drops the selection just as thoroughly. Re-asserting once per
|
|
1197
|
+
* render pass is what keeps it right, and a select carries one binding, so it is one push.
|
|
1198
|
+
*/
|
|
1199
|
+
if (this._select) {
|
|
474
1200
|
this._committed = value;
|
|
1201
|
+
/** Adoption never re-asserts a form value — the person may have changed it. See below. */
|
|
1202
|
+
if (!(false && adopting))
|
|
1203
|
+
(pendingSelects ??= []).push(this._element, value);
|
|
1204
|
+
return index + this._slots;
|
|
1205
|
+
}
|
|
1206
|
+
if (value !== this._committed) {
|
|
475
1207
|
if (kind === ATTR) {
|
|
1208
|
+
/**
|
|
1209
|
+
* A nullish value removes the attribute — except on the first commit of a template that
|
|
1210
|
+
* never statically wrote it, where a fresh clone has nothing to remove. That skip used to
|
|
1211
|
+
* be unconditional-removal instead, for the one case that genuinely needs it:
|
|
1212
|
+
* `<b title="a" title=${null}>` parses keeping the first duplicate, so the binding —
|
|
1213
|
+
* written last, and authoritative on the server too — must clear it. `_present` is that
|
|
1214
|
+
* case, read off the parsed template once ever; without it the removal was a real DOM call
|
|
1215
|
+
* per nullish binding per element on create — 1,000 no-ops in the 1,000-row benchmark.
|
|
1216
|
+
*/
|
|
476
1217
|
if (value == null) {
|
|
477
|
-
if (
|
|
1218
|
+
if (this._present || this._committed !== UNSET)
|
|
478
1219
|
this._element.removeAttribute(this._name);
|
|
479
1220
|
}
|
|
480
|
-
else
|
|
1221
|
+
else {
|
|
1222
|
+
/**
|
|
1223
|
+
* The same question `@verajs/renderer/spread` asks at its own sink, from the same home —
|
|
1224
|
+
* the two are deliberately separate implementations (see spread's header on why), and a
|
|
1225
|
+
* diagnostic that lived in only one of them would be the very defect this audit found.
|
|
1226
|
+
* `setAttribute` performs the DOMString conversion itself; nothing is stringified here.
|
|
1227
|
+
*/
|
|
1228
|
+
if (true ) {
|
|
1229
|
+
const complaint = attributeValueComplaint(this._element.localName, this._name, value);
|
|
1230
|
+
if (complaint !== null)
|
|
1231
|
+
console.warn(`[vera] ${complaint}`);
|
|
1232
|
+
}
|
|
481
1233
|
this._element.setAttribute(this._name, value);
|
|
1234
|
+
}
|
|
482
1235
|
}
|
|
483
1236
|
else if (kind === PROPERTY) {
|
|
484
1237
|
const target = this._element;
|
|
485
1238
|
const name = this._name;
|
|
486
|
-
target[name] = value;
|
|
487
1239
|
/**
|
|
488
|
-
*
|
|
489
|
-
*
|
|
490
|
-
* A property set on a custom element that has not upgraded yet lands as an own property on
|
|
491
|
-
* the instance. When the definition arrives — lazily imported, code-split, or a module that
|
|
492
|
-
* simply had not run — `customElements.define` upgrades synchronously and the class's field
|
|
493
|
-
* initializers execute. At target ES2022 a field declaration is a `[[Define]]`, so
|
|
494
|
-
* `item?: T` emits `item;` and overwrites the bound value with `undefined`. Nothing throws;
|
|
495
|
-
* it reads as broken reactivity.
|
|
1240
|
+
* **Adopting a form value: record it, do not write it.**
|
|
496
1241
|
*
|
|
497
|
-
*
|
|
498
|
-
*
|
|
499
|
-
*
|
|
500
|
-
*
|
|
501
|
-
*
|
|
502
|
-
*
|
|
1242
|
+
* `value`, `checked` and `selected` are exactly the properties `@verajs/ssr` mirrors into
|
|
1243
|
+
* markup, so the element already holds what this binding says — *unless a person changed
|
|
1244
|
+
* it*, which is the entire reason to server-render: the page is usable before the bundle
|
|
1245
|
+
* lands, and the window between the two is where someone types their name, ticks a box or
|
|
1246
|
+
* picks an option. Writing the binding then threw that away, silently, on every hydrating
|
|
1247
|
+
* page. The part is told it already committed this value, so it stays live and the next
|
|
1248
|
+
* genuine state change still applies.
|
|
503
1249
|
*
|
|
504
|
-
*
|
|
505
|
-
* `
|
|
506
|
-
* throws (`lit.dev/msg/class-field-shadowing`); a warning suffices here because Vera has no
|
|
507
|
-
* prototype accessors to shadow permanently — the damage is one lost value, not a property
|
|
508
|
-
* that never updates again.
|
|
1250
|
+
* Only these three, and only while adopting. A property the server cannot express — any
|
|
1251
|
+
* other `.prop` — is not in the DOM yet and must be written.
|
|
509
1252
|
*/
|
|
510
|
-
if (
|
|
511
|
-
|
|
512
|
-
|
|
513
|
-
customElements.whenDefined(tag).then(() => {
|
|
514
|
-
/**
|
|
515
|
-
* States what was observed rather than diagnosing it. A class field is the usual
|
|
516
|
-
* cause by a wide margin, but a component that assigns the property itself during
|
|
517
|
-
* upgrade produces the same observation, and that is a legitimate — if confusing —
|
|
518
|
-
* thing to do, since the renderer's dirty check will not re-apply the bound value on
|
|
519
|
-
* the next render either.
|
|
520
|
-
*/
|
|
521
|
-
if (target[name] !== value)
|
|
522
|
-
console.warn(`@verajs/renderer: the value bound by \`.${name}=\${…}\` on <${tag}> was replaced ` +
|
|
523
|
-
`while the element upgraded. A class field is the usual cause: at ES2022 ` +
|
|
524
|
-
`\`${name}?: …\` emits \`${name};\`, which runs during upgrade and overwrites ` +
|
|
525
|
-
`whatever was set beforehand — write it \`declare ${name}?: …\` instead, which ` +
|
|
526
|
-
`emits nothing. A plain field also wipes properties assigned imperatively, ` +
|
|
527
|
-
`which cannot be detected at all. Ignore this if the component replaced the ` +
|
|
528
|
-
`value on purpose.`);
|
|
529
|
-
});
|
|
530
|
-
}
|
|
1253
|
+
if (false && adopting && (name === 'value' || name === 'checked' || name === 'selected')) {
|
|
1254
|
+
this._committed = value;
|
|
1255
|
+
return index + this._slots;
|
|
531
1256
|
}
|
|
1257
|
+
/**
|
|
1258
|
+
* No un-upgraded custom element can be behind this write: a dash-named property part is
|
|
1259
|
+
* born `PROP_ADOPT` and only flips here once something receives the property, so the
|
|
1260
|
+
* pre-upgrade window — the clobber, its repair for components, and the `whenDefined`
|
|
1261
|
+
* detector for elements that never drain — lives entirely in `commitAdopt` above. History
|
|
1262
|
+
* worth keeping: an earlier repair was tried HERE and removed as silently partial (it
|
|
1263
|
+
* re-applied on `undefined`, so `item = someDefault` never looked clobbered); the record
|
|
1264
|
+
* the drain re-applies unconditionally is what answered that objection.
|
|
1265
|
+
*/
|
|
1266
|
+
target[name] = value;
|
|
532
1267
|
}
|
|
533
1268
|
else if (kind === BOOLEAN) {
|
|
534
|
-
|
|
535
|
-
|
|
1269
|
+
/** Unconditional for the same reason: `<b hidden ?hidden=${false}>` must end up not hidden. */
|
|
1270
|
+
this._element.toggleAttribute(this._name, !!value);
|
|
536
1271
|
}
|
|
537
1272
|
else if (kind === EVENT) {
|
|
1273
|
+
/**
|
|
1274
|
+
* A listener is the most deferred call a template makes — it is validated when a *user*
|
|
1275
|
+
* clicks, which in development may be never. So it is checked where it is written, the same
|
|
1276
|
+
* rule the setters took on: the stack at dispatch no longer contains the binding.
|
|
1277
|
+
*
|
|
1278
|
+
* `false` is deliberately allowed and silent. `@click=${enabled && onClick}` is the ordinary
|
|
1279
|
+
* way to bind conditionally and produces exactly that, and it already behaves correctly —
|
|
1280
|
+
* `handleEvent` finds nothing callable and does nothing. `true` is not produced by any
|
|
1281
|
+
* idiom, so it is named along with strings, numbers and objects that cannot listen.
|
|
1282
|
+
*/
|
|
1283
|
+
if (true && value != null && value !== false && typeof value !== 'function' &&
|
|
1284
|
+
typeof value?.handleEvent !== 'function')
|
|
1285
|
+
console.warn(`[vera] @${this._name} on <${this._element.localName}> was given ${typeof value === 'object' ? 'an object with no handleEvent method' : `a ${typeof value}`}, ` +
|
|
1286
|
+
`which cannot listen — the event will do nothing.\n` +
|
|
1287
|
+
`Pass a function, or an object with a handleEvent method. A missing handler is ` +
|
|
1288
|
+
`\`undefined\` or \`false\`, both of which are fine; this is neither.`);
|
|
538
1289
|
if (this._handler === null && value != null)
|
|
539
1290
|
this._element.addEventListener(this._name, this);
|
|
540
1291
|
this._handler = value ?? null;
|
|
541
1292
|
}
|
|
1293
|
+
else if (kind === PROP_ADOPT) {
|
|
1294
|
+
const next = commitAdopt(this._element, this._name, value);
|
|
1295
|
+
if (next !== 0)
|
|
1296
|
+
this._kind = next;
|
|
1297
|
+
}
|
|
542
1298
|
else if (value != null) {
|
|
543
1299
|
/**
|
|
544
1300
|
* Element ref: `<input ${myRef} />`. A function is called with the element; an object gets
|
|
545
1301
|
* the element assigned to `.value` — which makes core's own `ref()` double as an element
|
|
546
1302
|
* ref, reactively. Runs once per distinct value, not once per render.
|
|
547
1303
|
*/
|
|
1304
|
+
notifyOnRemoval = true;
|
|
548
1305
|
if (typeof value === 'function')
|
|
549
|
-
value
|
|
1306
|
+
applyRef(value, this._element);
|
|
550
1307
|
else if (typeof value === 'object') {
|
|
551
1308
|
/**
|
|
552
1309
|
* A self-applying value: anything that knows what to do with an element applies itself.
|
|
@@ -566,16 +1323,90 @@ class AttrPart {
|
|
|
566
1323
|
}
|
|
567
1324
|
// any other value type at element position is consumed and ignored
|
|
568
1325
|
}
|
|
1326
|
+
this._committed = value;
|
|
569
1327
|
}
|
|
570
1328
|
return index + this._slots;
|
|
571
1329
|
}
|
|
572
1330
|
}
|
|
1331
|
+
/**
|
|
1332
|
+
* `<select>.value` assignments held until the whole pass has committed — see the note in `_commit`.
|
|
1333
|
+
* Flat pairs rather than tuples: one array, no per-entry allocation.
|
|
1334
|
+
*/
|
|
1335
|
+
let pendingSelects = null;
|
|
1336
|
+
const flushSelects = () => {
|
|
1337
|
+
const queued = pendingSelects;
|
|
1338
|
+
if (queued === null)
|
|
1339
|
+
return;
|
|
1340
|
+
/** Cleared first: an assignment can run a `change` handler that renders again. */
|
|
1341
|
+
pendingSelects = null;
|
|
1342
|
+
for (let i = 0; i < queued.length; i += 2)
|
|
1343
|
+
queued[i].value = queued[i + 1];
|
|
1344
|
+
};
|
|
1345
|
+
const SCRATCH = doc.createDocumentFragment();
|
|
1346
|
+
/**
|
|
1347
|
+
* Marks a node as the render root's OWN output — see `ChildPart._insert`. Sigil-named so property
|
|
1348
|
+
* mangling cannot rename it: this is read by `@verajs/renderer/slots`, across a bundle boundary,
|
|
1349
|
+
* and a module-scoped Symbol would be minted twice on a CDN page (the `@verajs/styles` lesson).
|
|
1350
|
+
*
|
|
1351
|
+
* A fragment is stamped through to its children, because inserting one moves the children and the
|
|
1352
|
+
* fragment itself never enters the document — the observer reports the children.
|
|
1353
|
+
*
|
|
1354
|
+
* **Defined rather than assigned, so it is NON-ENUMERABLE.** A plain `node._$own$ = true` is an own
|
|
1355
|
+
* enumerable property: measured, it then shows up in `Object.keys(element)` — which is `[]` for
|
|
1356
|
+
* every other DOM element — and in `for…in`. Invisibility to everything outside the framework is
|
|
1357
|
+
* the whole reason this is a property and not a marker or an attribute, and an enumerable one is
|
|
1358
|
+
* not invisible. The descriptor is shared, so this allocates nothing per node, and the path is
|
|
1359
|
+
* gated on slots being wired, so no app that does not use them ever reaches it.
|
|
1360
|
+
*/
|
|
1361
|
+
const OWN_DESCRIPTOR = { value: true, enumerable: false, configurable: true, writable: true };
|
|
1362
|
+
/**
|
|
1363
|
+
* The stamp is VALUED, and the value is the discriminator (`docs` in the slots module read it):
|
|
1364
|
+
*
|
|
1365
|
+
* `true` — the render root's own output: never slot content.
|
|
1366
|
+
* a ChildPart — light content PLACED by that part from an outer template. The part identity
|
|
1367
|
+
* is the ordering group: a grown row belongs after ITS part's other rows, and
|
|
1368
|
+
* `<host>${a}${b}</host>` must not interleave a's refill into b's content —
|
|
1369
|
+
* which is exactly what happens if the group is the render root, shared by both.
|
|
1370
|
+
* absent — an imperative user mutation; the light region orders it by document position.
|
|
1371
|
+
*
|
|
1372
|
+
* One shared, mutated descriptor: `defineProperty` reads it synchronously, so this allocates
|
|
1373
|
+
* nothing per node while keeping the property non-enumerable (see the invisibility note above).
|
|
1374
|
+
*/
|
|
1375
|
+
const stampOwn = (node, value = true) => {
|
|
1376
|
+
OWN_DESCRIPTOR.value = value;
|
|
1377
|
+
if (node.nodeType === 11) {
|
|
1378
|
+
for (let child = node.firstChild; child !== null; child = child.nextSibling)
|
|
1379
|
+
Object.defineProperty(child, '_$own$', OWN_DESCRIPTOR);
|
|
1380
|
+
return;
|
|
1381
|
+
}
|
|
1382
|
+
Object.defineProperty(node, '_$own$', OWN_DESCRIPTOR);
|
|
1383
|
+
};
|
|
1384
|
+
/** A row is either an element-mode instance or a markered part; both can hold appliers. */
|
|
1385
|
+
const detachItem = (item) => {
|
|
1386
|
+
item._instance?._teardown();
|
|
1387
|
+
item._part?._detach();
|
|
1388
|
+
};
|
|
573
1389
|
class Instance {
|
|
574
1390
|
_parts = [];
|
|
575
1391
|
_fragment;
|
|
576
1392
|
constructor(template) {
|
|
577
|
-
/**
|
|
578
|
-
|
|
1393
|
+
/**
|
|
1394
|
+
* `importNode`, not `cloneNode` — the difference is custom-element upgrade, not the document.
|
|
1395
|
+
* Template content lives in the inert template document, so `cloneNode` copies stay
|
|
1396
|
+
* un-upgraded until insertion; a `.prop` committed in that window lands as an OWN property
|
|
1397
|
+
* that permanently shadows a defined class's setter (the setter never fires — every
|
|
1398
|
+
* accessor-based element, Lit's included, receives a dead value) and a bound value on a
|
|
1399
|
+
* class-field element is clobbered by the field initializer at insert, silently, because the
|
|
1400
|
+
* `whenDefined` detector below only watches definitions that arrive LATE. Hydration commits
|
|
1401
|
+
* onto server-parsed, already-upgraded elements, so the two render paths disagreed about the
|
|
1402
|
+
* same template. `importNode`'s cloning steps upgrade defined elements at clone time — in
|
|
1403
|
+
* every engine and in jsdom — which makes the commit order match hydration and the platform.
|
|
1404
|
+
* Undefined elements are untouched: nothing can upgrade them, and the pre-upgrade posture
|
|
1405
|
+
* (own property, clobber on define, development warning) stands as pinned in
|
|
1406
|
+
* `tests/pre-upgrade-property.test.mjs`. Measured cost of losing `cloneNode`: ~2–7% of the
|
|
1407
|
+
* raw clone operation across the three engines — nanoseconds per instance.
|
|
1408
|
+
*/
|
|
1409
|
+
this._fragment = doc.importNode(template._element.content, true);
|
|
579
1410
|
const templateParts = template._parts;
|
|
580
1411
|
/** Shared walker, ELEMENT | TEXT — child anchors are the primed text nodes themselves. */
|
|
581
1412
|
instanceWalker.currentNode = this._fragment;
|
|
@@ -593,14 +1424,130 @@ class Instance {
|
|
|
593
1424
|
}
|
|
594
1425
|
this._parts.push(templatePart._type === CHILD
|
|
595
1426
|
? new TextPart(node)
|
|
596
|
-
: new AttrPart(node, templatePart._name, templatePart._statics));
|
|
1427
|
+
: new AttrPart(node, templatePart._name, templatePart._statics, templatePart._present));
|
|
1428
|
+
}
|
|
1429
|
+
/**
|
|
1430
|
+
* Slot records mount OUTSIDE the parts array — one extra walk from the top, paid only by
|
|
1431
|
+
* templates that HAVE slots, only inside a renderInto commit (null root — hydration's
|
|
1432
|
+
* adoption path — stays inert), and only when the 'slot' insert answers. Taking over sets
|
|
1433
|
+
* `notifyOnRemoval`: `_$park$` must rescue the USER'S nodes before a bulk `_clear` discards
|
|
1434
|
+
* the DOM holding them on a branch-away. `_update` never sees any of this.
|
|
1435
|
+
*/
|
|
1436
|
+
if (template._seam !== undefined && _slotRoot !== null) {
|
|
1437
|
+
const slotRecords = template._slots;
|
|
1438
|
+
/**
|
|
1439
|
+
* RESOLVE every slot element to its clone in ONE walk, and mount them AFTER the first
|
|
1440
|
+
* `_update` — see `_mountSlots`. Collect-then-act, because the seam MUTATES the fragment
|
|
1441
|
+
* (it lifts each `<slot>` out and drops in anchors) and a walk that interleaved resolution
|
|
1442
|
+
* with those mutations would read shifted indices and miss later slots.
|
|
1443
|
+
*/
|
|
1444
|
+
instanceWalker.currentNode = this._fragment;
|
|
1445
|
+
nodeIndex = -1;
|
|
1446
|
+
const slotNodes = [];
|
|
1447
|
+
for (let i = 0; i < slotRecords.length; i++) {
|
|
1448
|
+
while (nodeIndex < slotRecords[i]) {
|
|
1449
|
+
node = instanceWalker.nextNode();
|
|
1450
|
+
nodeIndex++;
|
|
1451
|
+
}
|
|
1452
|
+
slotNodes.push(node);
|
|
1453
|
+
}
|
|
1454
|
+
this._pendingSlots = slotNodes;
|
|
1455
|
+
}
|
|
1456
|
+
/** Standalone rather than an `else` branch: `_slotless` is only ever set when there was no
|
|
1457
|
+
* seam, so the condition stands alone — and a lone `if (true …)` folds away cleanly. */
|
|
1458
|
+
if (true && template._slotless === true && _slotRoot !== null && _slotRoot.nodeType === 1) {
|
|
1459
|
+
/**
|
|
1460
|
+
* **A `<slot>` in a LIGHT render that nothing will distribute.** Both ways of arriving here
|
|
1461
|
+
* are silent otherwise, and both leave the same confusing picture. Measured, for a host given
|
|
1462
|
+
* `<b slot="a">MINE</b>`:
|
|
1463
|
+
*
|
|
1464
|
+
* <b slot="a">MINE</b><!----><div class="box"><slot name="a">FB</slot></div>
|
|
1465
|
+
*
|
|
1466
|
+
* — the content is not destroyed, it is stranded ahead of the render while the slot shows its
|
|
1467
|
+
* fallback. The message says "any content the host is given" rather than asserting the host
|
|
1468
|
+
* HAS some: a component that consumes its own children before rendering and also declares
|
|
1469
|
+
* slots — `@verajs/ui`'s select is one — warns with nothing stray on the page, and a reader
|
|
1470
|
+
* sent looking for markup that is not there concludes the diagnostic is confused.
|
|
1471
|
+
*
|
|
1472
|
+
* 1. `@verajs/renderer/slots` was never wired at all.
|
|
1473
|
+
* 2. It was wired AFTER this template first rendered. Templates are interned per call site
|
|
1474
|
+
* for the life of the page and resolve the seam once, at construction — so a component
|
|
1475
|
+
* that rendered before the wiring keeps a slotless template forever, and every later use
|
|
1476
|
+
* of it fails the same way. Measured: the same `draw()` distributes at a fresh call site
|
|
1477
|
+
* and not at this one.
|
|
1478
|
+
*
|
|
1479
|
+
* A shadow root never reaches here: the platform slots there, which is why this is gated on
|
|
1480
|
+
* an element root.
|
|
1481
|
+
*/
|
|
1482
|
+
warnSlotless(_slotRoot);
|
|
597
1483
|
}
|
|
598
1484
|
}
|
|
1485
|
+
/**
|
|
1486
|
+
* One walk, both jobs: release the element refs in this instance and tell any child applier
|
|
1487
|
+
* under it that it is going away.
|
|
1488
|
+
*
|
|
1489
|
+
* They were two walks over the same array — `_release` for refs, `_detach` for appliers — which
|
|
1490
|
+
* is the same tree traversed twice for two answers that arrive at the same moment. Merged, the
|
|
1491
|
+
* per-part cost is one `_kind` compare and one `_upgraded` read.
|
|
1492
|
+
*
|
|
1493
|
+
* Reached only when this instance's template holds a ref, or some applier somewhere declared
|
|
1494
|
+
* teardown. An app with neither never runs it: this is the per-node work the bulk removal exists
|
|
1495
|
+
* to skip, and the gate is what keeps it out of the path.
|
|
1496
|
+
*
|
|
1497
|
+
* Through `_upgraded`, not just `_parts`. A child position is instantiated as a `TextPart` and
|
|
1498
|
+
* **upgrades** to a `ChildPart` the first time it takes an object — so the part holding a
|
|
1499
|
+
* applier is almost never the one in this array, it is the one that array's entry points at.
|
|
1500
|
+
* Walking `_parts` alone found nothing at all.
|
|
1501
|
+
*/
|
|
1502
|
+
_teardown() {
|
|
1503
|
+
const parts = this._parts;
|
|
1504
|
+
for (let i = 0; i < parts.length; i++) {
|
|
1505
|
+
const part = parts[i];
|
|
1506
|
+
if (part._kind === REF)
|
|
1507
|
+
part._release();
|
|
1508
|
+
part._upgraded?._detach();
|
|
1509
|
+
}
|
|
1510
|
+
/** Taken-over slots park the USER'S nodes before this instance's DOM is discarded. */
|
|
1511
|
+
this._slotStates?.forEach((state) => state._$park$?.());
|
|
1512
|
+
}
|
|
599
1513
|
_update(values) {
|
|
600
1514
|
let valueIndex = 0;
|
|
601
1515
|
const parts = this._parts;
|
|
602
1516
|
for (let i = 0; i < parts.length; i++)
|
|
603
1517
|
valueIndex = parts[i]._commit(values, valueIndex);
|
|
1518
|
+
if (this._pendingSlots !== undefined)
|
|
1519
|
+
this._mountSlots();
|
|
1520
|
+
}
|
|
1521
|
+
/**
|
|
1522
|
+
* **Slots mount after the first `_update`, not during construction, because a `<slot>`'s own
|
|
1523
|
+
* bindings are part of its meaning.** `<slot name=${section}>` has no name at all until its
|
|
1524
|
+
* `AttrPart` has committed, and mounting first read the static markup and got `''` — the slot
|
|
1525
|
+
* registered as a second DEFAULT slot, took the default content, and left the real default slot
|
|
1526
|
+
* showing fallback. Committing first also means `@slotchange` and `&ref` are already attached to
|
|
1527
|
+
* the element by the time anything is dispatched on it.
|
|
1528
|
+
*
|
|
1529
|
+
* Once per instance: the fields are cleared here and every later `_update` costs one compare.
|
|
1530
|
+
*/
|
|
1531
|
+
_mountSlots() {
|
|
1532
|
+
const slotNodes = this._pendingSlots;
|
|
1533
|
+
this._pendingSlots = undefined;
|
|
1534
|
+
/**
|
|
1535
|
+
* `_slotRoot` still holds the container: it is set for the whole of one `renderInto` and every
|
|
1536
|
+
* instance under it — nested templates included — is constructed and first-updated inside that
|
|
1537
|
+
* same synchronous span, so this is the root the constructor saw.
|
|
1538
|
+
*/
|
|
1539
|
+
const root = _slotRoot;
|
|
1540
|
+
const seam = slotSeam();
|
|
1541
|
+
if (seam === undefined || root === null)
|
|
1542
|
+
return;
|
|
1543
|
+
for (let i = 0; i < slotNodes.length; i++) {
|
|
1544
|
+
const slot = slotNodes[i];
|
|
1545
|
+
const state = seam(slot, root, slot.getAttribute('name') ?? '');
|
|
1546
|
+
if (state != null) {
|
|
1547
|
+
(this._slotStates ??= []).push(state);
|
|
1548
|
+
notifyOnRemoval = true;
|
|
1549
|
+
}
|
|
1550
|
+
}
|
|
604
1551
|
}
|
|
605
1552
|
}
|
|
606
1553
|
/** A single property read — this runs once per list item per render, so it must be minimal. */
|
|
@@ -636,9 +1583,26 @@ class TextPart {
|
|
|
636
1583
|
*/
|
|
637
1584
|
const start = comment();
|
|
638
1585
|
const end = comment();
|
|
639
|
-
|
|
640
|
-
|
|
641
|
-
|
|
1586
|
+
/**
|
|
1587
|
+
* **Markers go where the part LIVES, which is not always where its text node is.** In a
|
|
1588
|
+
* light host wired for slots, this text node was captured and distributed into the
|
|
1589
|
+
* component's tree — planting markers beside it there put them inside the slot's range,
|
|
1590
|
+
* the slot's next fill swept them into the holding fragment, and the part spent the rest
|
|
1591
|
+
* of the page rendering into detached space (measured: `<host>${text}</host>` toggling
|
|
1592
|
+
* through null showed FALLBACK forever). `_$home$` answers with the host's light-region
|
|
1593
|
+
* sentinel for a captured node and null for everything else, so every app without light
|
|
1594
|
+
* slots takes the second branch untouched.
|
|
1595
|
+
*/
|
|
1596
|
+
const home = slotSeam()?._$home$?.(this._text) ?? null;
|
|
1597
|
+
const parent = home !== null ? home.parentNode : this._text.parentNode;
|
|
1598
|
+
if (home !== null) {
|
|
1599
|
+
parent.insertBefore(start, home);
|
|
1600
|
+
parent.insertBefore(end, home);
|
|
1601
|
+
}
|
|
1602
|
+
else {
|
|
1603
|
+
parent.insertBefore(start, this._text);
|
|
1604
|
+
parent.insertBefore(end, this._text.nextSibling);
|
|
1605
|
+
}
|
|
642
1606
|
const part = new ChildPart(start, end);
|
|
643
1607
|
part._mode = TEXT;
|
|
644
1608
|
part._text = this._text;
|
|
@@ -654,11 +1618,70 @@ class TextPart {
|
|
|
654
1618
|
return index + 1;
|
|
655
1619
|
}
|
|
656
1620
|
}
|
|
1621
|
+
/**
|
|
1622
|
+
* The registry this renderer reads `'value'` handlers from, handed over by {@link renderer}.
|
|
1623
|
+
*
|
|
1624
|
+
* Not imported. The renderer carries no registry of its own for the same reason the router does
|
|
1625
|
+
* not: a production bundle inlines `@verajs/inserts`, so importing it would give this package one
|
|
1626
|
+
* registry and core another, and an app would register into whichever it happened to import — the
|
|
1627
|
+
* failure `connectInserts` used to repair.
|
|
1628
|
+
*/
|
|
1629
|
+
let registry = null;
|
|
1630
|
+
/**
|
|
1631
|
+
* The ONE lookup for the `'slot'` insert. Three callers want the same thing in the same shape —
|
|
1632
|
+
* template construction (are there slots to record?), the first render into a container (capture
|
|
1633
|
+
* the host's children), and hydration's rescue (un-distribute before a mismatch discards) — and
|
|
1634
|
+
* the seam carries its cross-bundle members as sigil-named keys, which every caller had to spell
|
|
1635
|
+
* out again. One accessor, spelled once.
|
|
1636
|
+
*/
|
|
1637
|
+
/**
|
|
1638
|
+
* **Whether ANY app on this page wired light slots**, latched the first time the seam answers.
|
|
1639
|
+
*
|
|
1640
|
+
* The ownership stamp in `_insert`/`$c` exists only for `@verajs/renderer/slots` to read, and its
|
|
1641
|
+
* guard has to be free for everyone else — `_slotRoot` is set for every `renderInto`, so without
|
|
1642
|
+
* this an app with no slots at all would stamp every top-level node it renders, which for a list
|
|
1643
|
+
* at the root is a property write per ROW. One boolean instead, false for the life of a page that
|
|
1644
|
+
* never wires them.
|
|
1645
|
+
*/
|
|
1646
|
+
let slotsWired = false;
|
|
1647
|
+
const slotSeam = () => {
|
|
1648
|
+
const seam = registry?.get('slot')?.[0];
|
|
1649
|
+
if (seam !== undefined)
|
|
1650
|
+
slotsWired = true;
|
|
1651
|
+
return seam;
|
|
1652
|
+
};
|
|
1653
|
+
const noHandlers = [];
|
|
1654
|
+
const valueHandlers = () => (registry ? (registry.get('value') ?? noHandlers) : noHandlers);
|
|
1655
|
+
/**
|
|
1656
|
+
* Kinds this package still ships. They read from a local list rather than the registry because the
|
|
1657
|
+
* renderer cannot register into one it was merely handed — that needs `wire`, which it does not
|
|
1658
|
+
* import. The list empties when they move to packages; until then a wired handler is checked first,
|
|
1659
|
+
* so a module can pre-empt a built-in exactly as the priority order promises.
|
|
1660
|
+
*/
|
|
1661
|
+
const builtIns = [];
|
|
1662
|
+
/**
|
|
1663
|
+
* Whether anything in this process has asked to be told when a subtree is removed — an element ref
|
|
1664
|
+
* to release, or a child applier that declared `_$detach$`.
|
|
1665
|
+
*
|
|
1666
|
+
* **One flag for both, and it is process-wide.** Teardown cannot be discovered from the template the
|
|
1667
|
+
* way a ref can — a ref is a `&` part the scan sees, while an applier arrives as a *value* and no
|
|
1668
|
+
* template shape predicts it — so the coarser gate is the only one that serves both.
|
|
1669
|
+
*
|
|
1670
|
+
* The finer, per-template gate for refs was measured and dropped: it saved 34 B less than nothing,
|
|
1671
|
+
* because the walk it avoided is not the expensive part. With one unrelated ref on the page, a
|
|
1672
|
+
* 1 000-row clear walks 1 000 instances and measures 3.98 ms against 4.03 ms with no ref at all —
|
|
1673
|
+
* the DOM removal dominates completely. What matters is that an app asking for neither walks
|
|
1674
|
+
* **zero**, and that still holds.
|
|
1675
|
+
*/
|
|
1676
|
+
let notifyOnRemoval = false;
|
|
1677
|
+
|
|
1678
|
+
const _applierSwaps = /* @__PURE__ */ new WeakMap();
|
|
657
1679
|
/** What a ChildPart currently contains. */
|
|
658
1680
|
const EMPTY = 0;
|
|
659
1681
|
const TEXT = 1;
|
|
660
1682
|
const TEMPLATE = 2;
|
|
661
1683
|
const LIST = 3;
|
|
1684
|
+
const NODE = 4;
|
|
662
1685
|
let _profileHook = null;
|
|
663
1686
|
class ChildPart {
|
|
664
1687
|
_start;
|
|
@@ -674,6 +1697,10 @@ class ChildPart {
|
|
|
674
1697
|
_keyedList = false;
|
|
675
1698
|
/** Held instances by template identity; survives clears so state outlives interim content. */
|
|
676
1699
|
_held = null;
|
|
1700
|
+
/** Whatever the last `_$child$` at this part returned — its continuity across renders. */
|
|
1701
|
+
_applierState = undefined;
|
|
1702
|
+
/** Which applier that state belongs to, so two of them at one part cannot read each other's. */
|
|
1703
|
+
_applier = undefined;
|
|
677
1704
|
constructor(start, end) {
|
|
678
1705
|
this._start = start;
|
|
679
1706
|
this._end = end;
|
|
@@ -682,13 +1709,117 @@ class ChildPart {
|
|
|
682
1709
|
this._set(values[index]);
|
|
683
1710
|
return index + 1;
|
|
684
1711
|
}
|
|
1712
|
+
/**
|
|
1713
|
+
* **A component's own output is STAMPED, so the slot system cannot mistake it for content.**
|
|
1714
|
+
*
|
|
1715
|
+
* `@verajs/renderer/slots` captures a top-level element carrying a `slot` attribute as the
|
|
1716
|
+
* host's content — which a component's own rendered root may legitimately be, when it renders
|
|
1717
|
+
* something destined for ITS parent's slot. Measured: with slots wired,
|
|
1718
|
+
* `renderInto(html\`<div slot="x">…</div>\`, element)` distributed the component's output into
|
|
1719
|
+
* its own holding fragment and the component rendered NOTHING, on the first render, with no
|
|
1720
|
+
* children involved and nothing thrown.
|
|
1721
|
+
*
|
|
1722
|
+
* The renderer is the one party that knows: it is inserting at the top level of the container
|
|
1723
|
+
* it was asked to render into. `_slotRoot` is that container for the whole of one `renderInto`,
|
|
1724
|
+
* so `parent === _slotRoot` is exactly "this is the component's own output" and distinguishes it
|
|
1725
|
+
* from `<x-card>${value}</x-card>`, where the part's parent is the host but the render root is
|
|
1726
|
+
* an ancestor — the user's light content, which must still be captured.
|
|
1727
|
+
*
|
|
1728
|
+
* Two comparisons on a path that is already touching the DOM, and the stamp is a PROPERTY:
|
|
1729
|
+
* invisible to CSS, to serialization and to `children`, unlike any marker or attribute, and it
|
|
1730
|
+
* rides on text nodes, which no attribute can. An app without slots wired writes it and nothing
|
|
1731
|
+
* ever reads it.
|
|
1732
|
+
*/
|
|
1733
|
+
/**
|
|
1734
|
+
* **One property read decides all stamping, and root-part-ness decides the value.**
|
|
1735
|
+
*
|
|
1736
|
+
* `_$hosted$` is set on the host element itself by `@verajs/renderer/slots` at capture, so
|
|
1737
|
+
* "does anything care about ownership here" is a single own-property read — no seam call, no
|
|
1738
|
+
* registry lookup, and pages that are not captured hosts (every container in most apps) cost
|
|
1739
|
+
* exactly that read and write nothing. The mark cannot go stale in the direction that matters:
|
|
1740
|
+
* a part's first commit runs in a detached fragment before its host is captured, reads
|
|
1741
|
+
* `undefined`, and stamps nothing — and that content is exactly what the initial capture walk
|
|
1742
|
+
* lifts anyway. Every later commit sees the mark.
|
|
1743
|
+
*
|
|
1744
|
+
* The VALUE is structural, not temporal. `_end === null` is true of root parts alone (see
|
|
1745
|
+
* `_clear`), and a root part's inserts are by definition the render's own output — a fact that
|
|
1746
|
+
* stays true for an applier committing from a microtask hours after `renderInto` returned,
|
|
1747
|
+
* where the earlier `parent === _slotRoot` test read null and left ASYNC output unstamped for
|
|
1748
|
+
* the flipped capture rule to eat. Everything else inserting into a host is placing content
|
|
1749
|
+
* INTO it from outside, stamped with the part — the ordering group.
|
|
1750
|
+
*/
|
|
685
1751
|
_insert(node) {
|
|
686
|
-
this._start.parentNode
|
|
1752
|
+
const parent = this._start.parentNode;
|
|
1753
|
+
if (slotsWired && parent._$hosted$ === true)
|
|
1754
|
+
stampOwn(node, this._end === null ? true : this);
|
|
1755
|
+
parent.insertBefore(node, this._end);
|
|
1756
|
+
}
|
|
1757
|
+
/**
|
|
1758
|
+
* Tells every child applier under this part that it is going away.
|
|
1759
|
+
*
|
|
1760
|
+
* Reached only when some applier somewhere declared teardown — see `notifyOnRemoval` — because
|
|
1761
|
+
* this is the per-node walk the bulk removal exists to skip. **Every** removal path calls it, not
|
|
1762
|
+
* just `_clear`: a keyed row is dropped by moving its nodes to a scratch fragment and an index-mode
|
|
1763
|
+
* list shrinks by removing nodes directly, so a version that only hooked `_clear` notified a
|
|
1764
|
+
* applier when its container was replaced and stayed silent when its row was deleted — told
|
|
1765
|
+
* sometimes, which is a worse contract than never.
|
|
1766
|
+
*/
|
|
1767
|
+
_detach() {
|
|
1768
|
+
if (this._applier !== undefined)
|
|
1769
|
+
this._applier._$detach$?.(this._applierState);
|
|
1770
|
+
this._instance?._teardown();
|
|
1771
|
+
const items = this._items;
|
|
1772
|
+
if (items != null)
|
|
1773
|
+
for (let i = 0; i < items.length; i++)
|
|
1774
|
+
detachItem(items[i]);
|
|
687
1775
|
}
|
|
688
1776
|
_clear() {
|
|
1777
|
+
/**
|
|
1778
|
+
* One gate, two jobs. A template that holds an element ref must release it; a subtree holding a
|
|
1779
|
+
* applier that declared teardown must be told. Both are found by the same walk, and an app
|
|
1780
|
+
* with neither reads two booleans and walks nothing.
|
|
1781
|
+
*/
|
|
1782
|
+
if (notifyOnRemoval)
|
|
1783
|
+
this._detach();
|
|
689
1784
|
const parent = this._start.parentNode;
|
|
690
1785
|
const end = this._end;
|
|
1786
|
+
const items = this._items;
|
|
691
1787
|
/**
|
|
1788
|
+
* **Content that is no longer between the markers.** `@verajs/renderer/slots` distributes a
|
|
1789
|
+
* light host's children by MOVING them into the component's tree, so a part rendering those
|
|
1790
|
+
* children keeps its markers in the host while its content lives inside the component.
|
|
1791
|
+
*
|
|
1792
|
+
* Both branches below are wrong for that, and wrong in opposite directions. The walk finds
|
|
1793
|
+
* the markers adjacent and removes nothing — the content stays on screen after being cleared
|
|
1794
|
+
* (a template swap in a light host showed the OLD template forever). The whole-parent fast
|
|
1795
|
+
* path is the dangerous one: it would `textContent = ''` the HOST, component render and all.
|
|
1796
|
+
*
|
|
1797
|
+
* Every mode knows its content by IDENTITY, which is parent-agnostic and split-proof: items
|
|
1798
|
+
* through `$m`, TEXT through `_text`, NODE through `_value`, TEMPLATE through the top-level
|
|
1799
|
+
* node array recorded at commit. The one shape that cannot be found this way is a
|
|
1800
|
+
* DocumentFragment committed at NODE position (its children scatter and it keeps no record);
|
|
1801
|
+
* that falls through to the walk, as before.
|
|
1802
|
+
*/
|
|
1803
|
+
if (this._start.nextSibling === end && this._mode !== EMPTY) {
|
|
1804
|
+
if (items !== null) {
|
|
1805
|
+
for (const item of items)
|
|
1806
|
+
if (item !== null)
|
|
1807
|
+
this.$m(item, null, SCRATCH);
|
|
1808
|
+
SCRATCH.textContent = '';
|
|
1809
|
+
}
|
|
1810
|
+
else if (this._mode === TEXT) {
|
|
1811
|
+
this._text?.remove();
|
|
1812
|
+
}
|
|
1813
|
+
else if (this._mode === TEMPLATE) {
|
|
1814
|
+
if (Array.isArray(this._value))
|
|
1815
|
+
for (const node of this._value)
|
|
1816
|
+
node.remove();
|
|
1817
|
+
}
|
|
1818
|
+
else if (this._mode === NODE && typeof this._value.remove === 'function') {
|
|
1819
|
+
this._value.remove();
|
|
1820
|
+
}
|
|
1821
|
+
}
|
|
1822
|
+
else /**
|
|
692
1823
|
* When this part owns its parent's entire contents, one `textContent = ''` replaces removing
|
|
693
1824
|
* every node individually. For a 1 000-row table body that is the difference between ~22 ms
|
|
694
1825
|
* (lit-html's per-node teardown) and ~5 ms.
|
|
@@ -700,8 +1831,7 @@ class ChildPart {
|
|
|
700
1831
|
* always owns an end marker, so `_end === null` alone never held for it.
|
|
701
1832
|
*
|
|
702
1833
|
* Re-appending both anchors in order restores the part's boundary exactly as it was.
|
|
703
|
-
*/
|
|
704
|
-
if (this._start.previousSibling === null && (end === null || end.nextSibling === null)) {
|
|
1834
|
+
*/ if (this._start.previousSibling === null && (end === null || end.nextSibling === null)) {
|
|
705
1835
|
parent.textContent = '';
|
|
706
1836
|
parent.appendChild(this._start);
|
|
707
1837
|
if (end !== null)
|
|
@@ -725,6 +1855,27 @@ class ChildPart {
|
|
|
725
1855
|
this._instance = null;
|
|
726
1856
|
this._items = null;
|
|
727
1857
|
this._shape = null;
|
|
1858
|
+
this._applierState = undefined;
|
|
1859
|
+
this._applier = undefined;
|
|
1860
|
+
}
|
|
1861
|
+
/**
|
|
1862
|
+
* How a child-position applier renders. Named to survive property mangling — `/^_[a-z]/` is the
|
|
1863
|
+
* pattern, and `_$…$` does not match it — because this is the half of the protocol that third
|
|
1864
|
+
* parties call.
|
|
1865
|
+
*/
|
|
1866
|
+
_$commit$(value) {
|
|
1867
|
+
/**
|
|
1868
|
+
* The applier's own state survives its own rendering. Committing different content usually
|
|
1869
|
+
* runs `_clear`, which drops the state so a part that was emptied by *anything else* cannot
|
|
1870
|
+
* hand an applier continuity it no longer has — but an applier rendering its own next value
|
|
1871
|
+
* has not gone away, and losing continuity there made `until()` fall back to its placeholder on
|
|
1872
|
+
* the render after it resolved.
|
|
1873
|
+
*/
|
|
1874
|
+
const applierState = this._applierState;
|
|
1875
|
+
const applier = this._applier;
|
|
1876
|
+
this._set(value);
|
|
1877
|
+
this._applierState = applierState;
|
|
1878
|
+
this._applier = applier;
|
|
728
1879
|
}
|
|
729
1880
|
_set(value) {
|
|
730
1881
|
if (value == null) {
|
|
@@ -761,7 +1912,7 @@ class ChildPart {
|
|
|
761
1912
|
* them, in practice), commit costs one identity compare before touching the values.
|
|
762
1913
|
*/
|
|
763
1914
|
if (this._shape === value.strings) {
|
|
764
|
-
if (true
|
|
1915
|
+
if (true && _profileHook)
|
|
765
1916
|
;
|
|
766
1917
|
this._instance._update(value.values);
|
|
767
1918
|
return;
|
|
@@ -771,24 +1922,92 @@ class ChildPart {
|
|
|
771
1922
|
* subtree below is about to be destroyed and rebuilt rather than updated. That is what
|
|
772
1923
|
* `?hidden=${…}` over a swapped subtree exists to avoid, and it is otherwise invisible.
|
|
773
1924
|
*/
|
|
774
|
-
if (true
|
|
1925
|
+
if (true && _profileHook) ;
|
|
775
1926
|
const template = getTemplate(value);
|
|
776
1927
|
if (this._mode !== EMPTY)
|
|
777
1928
|
this._clear();
|
|
778
1929
|
const instance = new Instance(template);
|
|
779
1930
|
instance._update(value.values);
|
|
1931
|
+
/**
|
|
1932
|
+
* The instance's top-level nodes, recorded while they are still in the fragment. `_value`
|
|
1933
|
+
* is unused in TEMPLATE mode, and this is what lets `_clear` and `hold`'s parking find the
|
|
1934
|
+
* content after `@verajs/renderer/slots` has moved it out of the marker range — per node,
|
|
1935
|
+
* parent-agnostic, so even content split across two slots comes back. Costs one small array
|
|
1936
|
+
* on a path that just built an Instance and cloned a template; same-shape updates never
|
|
1937
|
+
* reach here.
|
|
1938
|
+
*/
|
|
1939
|
+
this._value = [...instance._fragment.childNodes];
|
|
780
1940
|
this._insert(instance._fragment);
|
|
781
1941
|
this._instance = instance;
|
|
782
1942
|
this._shape = value.strings;
|
|
783
1943
|
this._mode = TEMPLATE;
|
|
784
1944
|
return;
|
|
785
1945
|
}
|
|
786
|
-
|
|
787
|
-
|
|
1946
|
+
const handlers = valueHandlers();
|
|
1947
|
+
for (let i = 0; i < handlers.length; i++)
|
|
1948
|
+
if (handlers[i](this, value))
|
|
1949
|
+
return;
|
|
1950
|
+
for (let i = 0; i < builtIns.length; i++)
|
|
1951
|
+
if (builtIns[i](this, value))
|
|
1952
|
+
return;
|
|
1953
|
+
/**
|
|
1954
|
+
* **A child-position value that applies itself.** The same idea as `_$apply$` at element
|
|
1955
|
+
* position — which is how `@verajs/renderer/spread` ships as a separate package the renderer
|
|
1956
|
+
* knows nothing about — at the one other position worth extending.
|
|
1957
|
+
*
|
|
1958
|
+
* `_$child$(part, previous)` is handed the part and whatever it returned last time at this
|
|
1959
|
+
* part, and calls `part._$commit$(value)` to render content. Keeping continuity in the return
|
|
1960
|
+
* value rather than in an applier *instance* is what keeps this a protocol rather than a
|
|
1961
|
+
* framework: there is no base class, no factory and no lifecycle to learn, and an applier is
|
|
1962
|
+
* an object literal.
|
|
1963
|
+
*
|
|
1964
|
+
* Placed **after** the template check on purpose. A template is overwhelmingly the common
|
|
1965
|
+
* object at a child position, and it returns above without ever reading this property — so the
|
|
1966
|
+
* check costs the hot path nothing and only arrays, nodes and appliers pay for it. Measured:
|
|
1967
|
+
* +22 B gzipped, and no runtime difference distinguishable from noise.
|
|
1968
|
+
*
|
|
1969
|
+
* There is deliberately no teardown hook. `_clear` bulk-removes DOM and, when the part owns its
|
|
1970
|
+
* parent, does `parent.textContent = ''` — the thing that makes clearing a 1 000-row table ~5 ms
|
|
1971
|
+
* against lit-html's ~22 ms. Calling teardown on a nested applier would mean walking the part
|
|
1972
|
+
* tree on every removal, which is precisely the per-node work that fast path exists to skip. So
|
|
1973
|
+
* an applier here can render, and cannot yet be told it has gone away.
|
|
1974
|
+
*/
|
|
1975
|
+
const applyChild = value._$child$;
|
|
1976
|
+
if (applyChild !== undefined) {
|
|
1977
|
+
/** `previous` belongs to *this* applier; a different one at the same part starts fresh. */
|
|
1978
|
+
const previous = this._applier === applyChild ? this._applierState : undefined;
|
|
1979
|
+
|
|
1980
|
+
if (true && this._applier !== undefined && this._applier !== applyChild) {
|
|
1981
|
+
const swaps = (_applierSwaps.get(this) ?? 0) + 1;
|
|
1982
|
+
_applierSwaps.set(this, swaps);
|
|
1983
|
+
if (swaps === 3) {
|
|
1984
|
+
console.warn(`[vera] a child applier changed identity ${swaps} times at one part, so \`previous\` ` +
|
|
1985
|
+
`is always undefined and it restarts every render.\n` +
|
|
1986
|
+
`Hoist the applier — written as an object-literal method it is a new function per ` +
|
|
1987
|
+
`call:\n\n` +
|
|
1988
|
+
` function applyThing(part, previous) { … } // once, at module scope\n` +
|
|
1989
|
+
` const thing = (x) => ({ _$child$: applyThing, x }); // state on the object\n`);
|
|
1990
|
+
}
|
|
1991
|
+
}
|
|
1992
|
+
this._applier = applyChild;
|
|
1993
|
+
if (applyChild._$detach$ !== undefined)
|
|
1994
|
+
notifyOnRemoval = true;
|
|
1995
|
+
this._applierState = applyChild.call(value, this, previous);
|
|
788
1996
|
return;
|
|
789
1997
|
}
|
|
790
|
-
if (
|
|
791
|
-
|
|
1998
|
+
if (value.nodeType !== undefined) {
|
|
1999
|
+
/**
|
|
2000
|
+
* A DOM node renders as itself — a canvas a charting library owns, a `<template>`'s content,
|
|
2001
|
+
* an element built by hand. Placed after the template check and before the list check
|
|
2002
|
+
* because `nodeType` is one property read and nothing else that reaches here has one.
|
|
2003
|
+
*/
|
|
2004
|
+
if (this._mode !== NODE || this._value !== value) {
|
|
2005
|
+
if (this._mode !== EMPTY)
|
|
2006
|
+
this._clear();
|
|
2007
|
+
this._insert(value);
|
|
2008
|
+
this._value = value;
|
|
2009
|
+
this._mode = NODE;
|
|
2010
|
+
}
|
|
792
2011
|
return;
|
|
793
2012
|
}
|
|
794
2013
|
// any other object: render as text
|
|
@@ -802,13 +2021,21 @@ class ChildPart {
|
|
|
802
2021
|
}
|
|
803
2022
|
const held = (this._held ??= new Map());
|
|
804
2023
|
if (this._mode === TEMPLATE) {
|
|
805
|
-
/** Park the live nodes back in their instance's own (empty) fragment.
|
|
2024
|
+
/** Park the live nodes back in their instance's own (empty) fragment. When the range is
|
|
2025
|
+
* empty but content existed, slots relocated it — the recorded top-level nodes park it
|
|
2026
|
+
* from wherever it lives, split slots and holding included. */
|
|
806
2027
|
const fragment = this._instance._fragment;
|
|
807
|
-
|
|
808
|
-
|
|
809
|
-
|
|
810
|
-
|
|
811
|
-
|
|
2028
|
+
if (this._start.nextSibling === this._end && Array.isArray(this._value)) {
|
|
2029
|
+
for (const node of this._value)
|
|
2030
|
+
fragment.appendChild(node);
|
|
2031
|
+
}
|
|
2032
|
+
else {
|
|
2033
|
+
let node = this._start.nextSibling;
|
|
2034
|
+
while (node !== this._end) {
|
|
2035
|
+
const next = node.nextSibling;
|
|
2036
|
+
fragment.appendChild(node);
|
|
2037
|
+
node = next;
|
|
2038
|
+
}
|
|
812
2039
|
}
|
|
813
2040
|
held.set(this._shape, this._instance);
|
|
814
2041
|
}
|
|
@@ -817,6 +2044,7 @@ class ChildPart {
|
|
|
817
2044
|
}
|
|
818
2045
|
const instance = held.get(result.strings) ?? new Instance(getTemplate(result));
|
|
819
2046
|
instance._update(result.values);
|
|
2047
|
+
this._value = [...instance._fragment.childNodes];
|
|
820
2048
|
this._insert(instance._fragment);
|
|
821
2049
|
this._instance = instance;
|
|
822
2050
|
this._shape = result.strings;
|
|
@@ -826,7 +2054,15 @@ class ChildPart {
|
|
|
826
2054
|
* Creates one list item. A single-root template instance becomes an element-mode item with no
|
|
827
2055
|
* markers at all; anything else gets its own start/end marker pair so moves can never dangle.
|
|
828
2056
|
*/
|
|
829
|
-
|
|
2057
|
+
$c(value, parent, ref) {
|
|
2058
|
+
/** Rows reach the DOM here rather than through `_insert`; same one-read gate, same
|
|
2059
|
+
* structural value — a root list's rows are the render's own output, any other part's rows
|
|
2060
|
+
* are content it places into the host, stamped with the part as the ordering group. */
|
|
2061
|
+
const stamp = slotsWired && parent._$hosted$ === true
|
|
2062
|
+
? this._end === null
|
|
2063
|
+
? true
|
|
2064
|
+
: this
|
|
2065
|
+
: null;
|
|
830
2066
|
if (value !== null && typeof value === 'object' && value.strings !== undefined) {
|
|
831
2067
|
const result = value;
|
|
832
2068
|
const template = getTemplate(result);
|
|
@@ -834,9 +2070,11 @@ class ChildPart {
|
|
|
834
2070
|
instance._update(result.values);
|
|
835
2071
|
const rootNode = instance._fragment.firstChild;
|
|
836
2072
|
if (rootNode !== null && rootNode.nodeType === 1 && rootNode.nextSibling === null) {
|
|
2073
|
+
if (stamp !== null)
|
|
2074
|
+
stampOwn(rootNode, stamp);
|
|
837
2075
|
parent.insertBefore(rootNode, ref);
|
|
838
2076
|
return {
|
|
839
|
-
|
|
2077
|
+
$k: result.key,
|
|
840
2078
|
_element: rootNode,
|
|
841
2079
|
_instance: instance,
|
|
842
2080
|
_shape: result.strings,
|
|
@@ -848,15 +2086,18 @@ class ChildPart {
|
|
|
848
2086
|
part._instance = instance;
|
|
849
2087
|
part._shape = result.strings;
|
|
850
2088
|
part._mode = TEMPLATE;
|
|
2089
|
+
part._value = [...instance._fragment.childNodes];
|
|
2090
|
+
if (stamp !== null)
|
|
2091
|
+
stampOwn(instance._fragment, stamp);
|
|
851
2092
|
part._start.parentNode.insertBefore(instance._fragment, part._end);
|
|
852
|
-
return {
|
|
2093
|
+
return { $k: result.key, _element: null, _instance: null, _shape: null, _part: part };
|
|
853
2094
|
}
|
|
854
2095
|
const part = createMarkeredPart(parent, ref);
|
|
855
2096
|
part._set(value);
|
|
856
|
-
return {
|
|
2097
|
+
return { $k: value?.key, _element: null, _instance: null, _shape: null, _part: part };
|
|
857
2098
|
}
|
|
858
2099
|
/** Commits a new value into an existing item, demoting element mode if the shape changed. */
|
|
859
|
-
|
|
2100
|
+
$u(item, value) {
|
|
860
2101
|
if (item._element !== null) {
|
|
861
2102
|
if (value !== null && typeof value === 'object' && value.strings === item._shape) {
|
|
862
2103
|
item._instance._update(value.values);
|
|
@@ -874,10 +2115,28 @@ class ChildPart {
|
|
|
874
2115
|
item._part._set(value);
|
|
875
2116
|
}
|
|
876
2117
|
/** The item's first node — its move/removal handle and the insertion reference before it. */
|
|
877
|
-
|
|
2118
|
+
$f(item) {
|
|
878
2119
|
return item._element ?? item._part._start;
|
|
879
2120
|
}
|
|
880
|
-
|
|
2121
|
+
/**
|
|
2122
|
+
* Moving and removing an item read `_element` and `_part`, which are mangled — so they stay here
|
|
2123
|
+
* rather than travelling with the algorithm that calls them. `$m` and `$d` are the price: two
|
|
2124
|
+
* cold methods, exempt from mangling, two characters each.
|
|
2125
|
+
*/
|
|
2126
|
+
$m(item, ref, parent = this._start.parentNode) {
|
|
2127
|
+
/**
|
|
2128
|
+
* **Already where it is going.** A reorder asks for many positions that are already correct,
|
|
2129
|
+
* and re-inserting a node that is in place is not free: it detaches and re-attaches, which
|
|
2130
|
+
* blurs focus, restarts a CSS transition and wakes every MutationObserver watching. The
|
|
2131
|
+
* relocated path below leans on this — it re-places every item rather than computing which
|
|
2132
|
+
* ones moved — but the ordinary two-ended diff gets the same saving.
|
|
2133
|
+
*
|
|
2134
|
+
* The item's LAST node is the one whose `nextSibling` decides this, and reading `_element` /
|
|
2135
|
+
* `_part._end` is why the check lives here rather than travelling with the algorithm.
|
|
2136
|
+
*/
|
|
2137
|
+
const last = item._element ?? item._part._end;
|
|
2138
|
+
if (last.nextSibling === ref && last.parentNode === parent)
|
|
2139
|
+
return;
|
|
881
2140
|
if (item._element !== null) {
|
|
882
2141
|
parent.insertBefore(item._element, ref);
|
|
883
2142
|
return;
|
|
@@ -891,8 +2150,10 @@ class ChildPart {
|
|
|
891
2150
|
}
|
|
892
2151
|
}
|
|
893
2152
|
/** Removal is a move into a scratch fragment that is immediately emptied. */
|
|
894
|
-
|
|
895
|
-
|
|
2153
|
+
$d(item) {
|
|
2154
|
+
if (notifyOnRemoval)
|
|
2155
|
+
detachItem(item);
|
|
2156
|
+
this.$m(item, null, SCRATCH);
|
|
896
2157
|
SCRATCH.textContent = '';
|
|
897
2158
|
}
|
|
898
2159
|
_commitList(newValues) {
|
|
@@ -912,7 +2173,7 @@ class ChildPart {
|
|
|
912
2173
|
}
|
|
913
2174
|
return;
|
|
914
2175
|
}
|
|
915
|
-
const isKeyed = newValues[0] != null && newValues[0]
|
|
2176
|
+
const isKeyed = newValues[0] != null && newValues[0].$r !== undefined;
|
|
916
2177
|
if (isKeyed !== this._keyedList && this._items.length) {
|
|
917
2178
|
this._clear();
|
|
918
2179
|
this._items = [];
|
|
@@ -925,7 +2186,7 @@ class ChildPart {
|
|
|
925
2186
|
/** Initial fill builds off-document and lands in one insert. */
|
|
926
2187
|
const fragment = doc.createDocumentFragment();
|
|
927
2188
|
for (let i = 0; i < count; i++)
|
|
928
|
-
items.push(this
|
|
2189
|
+
items.push(this.$c(newValues[i], fragment, null));
|
|
929
2190
|
this._insert(fragment);
|
|
930
2191
|
return;
|
|
931
2192
|
}
|
|
@@ -933,159 +2194,185 @@ class ChildPart {
|
|
|
933
2194
|
// index mode: update in place, grow at the end, shrink from the end
|
|
934
2195
|
const shared = items.length < count ? items.length : count;
|
|
935
2196
|
for (let i = 0; i < shared; i++)
|
|
936
|
-
this
|
|
2197
|
+
this.$u(items[i], newValues[i]);
|
|
937
2198
|
if (count > items.length) {
|
|
938
2199
|
const fragment = doc.createDocumentFragment();
|
|
939
2200
|
for (let i = items.length; i < count; i++)
|
|
940
|
-
items.push(this
|
|
2201
|
+
items.push(this.$c(newValues[i], fragment, null));
|
|
941
2202
|
this._insert(fragment);
|
|
942
2203
|
}
|
|
943
2204
|
else if (count < items.length) {
|
|
944
|
-
|
|
945
|
-
|
|
946
|
-
|
|
947
|
-
|
|
948
|
-
|
|
949
|
-
|
|
950
|
-
|
|
951
|
-
|
|
2205
|
+
if (notifyOnRemoval)
|
|
2206
|
+
for (let i = count; i < items.length; i++)
|
|
2207
|
+
detachItem(items[i]);
|
|
2208
|
+
/**
|
|
2209
|
+
* **Removed through the items, not by walking the range.** The walk this replaced ran from
|
|
2210
|
+
* the first doomed item to the last one's end and called `parent.removeChild` on each node,
|
|
2211
|
+
* which assumes every one of them is still a child of `parent`. `@verajs/renderer/slots`
|
|
2212
|
+
* moves a light host's children into the component's tree, and the walk then threw
|
|
2213
|
+
* `NotFoundError` out of the middle of a render — a plain `<x-card>${rows}</x-card>` losing
|
|
2214
|
+
* one row was enough, with no keyed list anywhere in it.
|
|
2215
|
+
*
|
|
2216
|
+
* `$m` into the scratch fragment is indifferent to where a node currently lives, and the
|
|
2217
|
+
* batch is dropped by one clear at the end, so the contiguous-run saving the walk was for
|
|
2218
|
+
* is kept.
|
|
2219
|
+
*/
|
|
2220
|
+
for (let i = count; i < items.length; i++)
|
|
2221
|
+
this.$m(items[i], null, SCRATCH);
|
|
2222
|
+
SCRATCH.textContent = '';
|
|
952
2223
|
items.length = count;
|
|
953
2224
|
}
|
|
954
2225
|
return;
|
|
955
2226
|
}
|
|
956
2227
|
/**
|
|
957
|
-
*
|
|
958
|
-
*
|
|
959
|
-
*
|
|
960
|
-
*
|
|
961
|
-
|
|
962
|
-
|
|
963
|
-
|
|
964
|
-
|
|
965
|
-
this._updateItem(items[i], newValues[i]);
|
|
966
|
-
i++;
|
|
967
|
-
}
|
|
968
|
-
if (i === count)
|
|
969
|
-
return;
|
|
970
|
-
}
|
|
971
|
-
/**
|
|
972
|
-
* Keyed reconciliation — the standard head/tail algorithm (as in lit's `repeat` and Vue):
|
|
973
|
-
* skip matching prefixes and suffixes, detect the two swap shapes directly, and fall back to
|
|
974
|
-
* key maps for arbitrary moves, removals and insertions.
|
|
2228
|
+
* Keyed reconciliation is not here. It lives in `@verajs/renderer/keyed`, and it arrives on
|
|
2229
|
+
* the values themselves — `keyed()` stamps each result with the strategy that understands it,
|
|
2230
|
+
* so importing the marker is what loads the algorithm. Nothing registers, nothing is wired, and
|
|
2231
|
+
* two strategies cannot disagree about a list because the list names its own.
|
|
2232
|
+
*
|
|
2233
|
+
* The protocol is three cold members (`$c`, `$u`, `$f`) plus a returned array. Everything a
|
|
2234
|
+
* strategy would otherwise have to reach for — the mode switch, the empty case, the initial
|
|
2235
|
+
* fill — is already done above and passed in.
|
|
975
2236
|
*/
|
|
976
|
-
|
|
977
|
-
const newKeys = new Array(count);
|
|
978
|
-
for (let i = 0; i < count; i++)
|
|
979
|
-
newKeys[i] = newValues[i].key;
|
|
980
|
-
const newItems = new Array(count);
|
|
981
|
-
let oldHead = 0;
|
|
982
|
-
let oldTail = oldItems.length - 1;
|
|
983
|
-
let newHead = 0;
|
|
984
|
-
let newTail = count - 1;
|
|
985
|
-
let newKeyToIndex;
|
|
986
|
-
let oldKeyToIndex;
|
|
987
|
-
const refAt = (i) => i < count && newItems[i] !== undefined ? this._firstNode(newItems[i]) : this._end;
|
|
988
|
-
while (oldHead <= oldTail && newHead <= newTail) {
|
|
989
|
-
if (oldItems[oldHead] === null)
|
|
990
|
-
oldHead++;
|
|
991
|
-
else if (oldItems[oldTail] === null)
|
|
992
|
-
oldTail--;
|
|
993
|
-
else if (oldItems[oldHead]._key === newKeys[newHead]) {
|
|
994
|
-
this._updateItem((newItems[newHead] = oldItems[oldHead]), newValues[newHead]);
|
|
995
|
-
oldHead++;
|
|
996
|
-
newHead++;
|
|
997
|
-
}
|
|
998
|
-
else if (oldItems[oldTail]._key === newKeys[newTail]) {
|
|
999
|
-
this._updateItem((newItems[newTail] = oldItems[oldTail]), newValues[newTail]);
|
|
1000
|
-
oldTail--;
|
|
1001
|
-
newTail--;
|
|
1002
|
-
}
|
|
1003
|
-
else if (oldItems[oldHead]._key === newKeys[newTail]) {
|
|
1004
|
-
const item = oldItems[oldHead];
|
|
1005
|
-
this._moveItem(item, refAt(newTail + 1));
|
|
1006
|
-
this._updateItem(item, newValues[newTail]);
|
|
1007
|
-
newItems[newTail] = item;
|
|
1008
|
-
oldHead++;
|
|
1009
|
-
newTail--;
|
|
1010
|
-
}
|
|
1011
|
-
else if (oldItems[oldTail]._key === newKeys[newHead]) {
|
|
1012
|
-
const item = oldItems[oldTail];
|
|
1013
|
-
this._moveItem(item, this._firstNode(oldItems[oldHead]));
|
|
1014
|
-
this._updateItem(item, newValues[newHead]);
|
|
1015
|
-
newItems[newHead] = item;
|
|
1016
|
-
oldTail--;
|
|
1017
|
-
newHead++;
|
|
1018
|
-
}
|
|
1019
|
-
else {
|
|
1020
|
-
if (newKeyToIndex === undefined) {
|
|
1021
|
-
newKeyToIndex = new Map();
|
|
1022
|
-
for (let i = newHead; i <= newTail; i++)
|
|
1023
|
-
newKeyToIndex.set(newKeys[i], i);
|
|
1024
|
-
oldKeyToIndex = new Map();
|
|
1025
|
-
for (let i = oldHead; i <= oldTail; i++) {
|
|
1026
|
-
if (oldItems[i] !== null)
|
|
1027
|
-
oldKeyToIndex.set(oldItems[i]._key, i);
|
|
1028
|
-
}
|
|
1029
|
-
}
|
|
1030
|
-
if (!newKeyToIndex.has(oldItems[oldHead]._key)) {
|
|
1031
|
-
this._dropItem(oldItems[oldHead]);
|
|
1032
|
-
oldHead++;
|
|
1033
|
-
}
|
|
1034
|
-
else if (!newKeyToIndex.has(oldItems[oldTail]._key)) {
|
|
1035
|
-
this._dropItem(oldItems[oldTail]);
|
|
1036
|
-
oldTail--;
|
|
1037
|
-
}
|
|
1038
|
-
else {
|
|
1039
|
-
const oldIndex = oldKeyToIndex.get(newKeys[newHead]);
|
|
1040
|
-
if (oldIndex === undefined) {
|
|
1041
|
-
newItems[newHead] = this._createItem(newValues[newHead], parent, this._firstNode(oldItems[oldHead]));
|
|
1042
|
-
}
|
|
1043
|
-
else {
|
|
1044
|
-
const item = oldItems[oldIndex];
|
|
1045
|
-
this._moveItem(item, this._firstNode(oldItems[oldHead]));
|
|
1046
|
-
this._updateItem(item, newValues[newHead]);
|
|
1047
|
-
newItems[newHead] = item;
|
|
1048
|
-
oldItems[oldIndex] = null;
|
|
1049
|
-
}
|
|
1050
|
-
newHead++;
|
|
1051
|
-
}
|
|
1052
|
-
}
|
|
1053
|
-
}
|
|
1054
|
-
while (newHead <= newTail) {
|
|
1055
|
-
newItems[newHead] = this._createItem(newValues[newHead], parent, refAt(newTail + 1));
|
|
1056
|
-
newHead++;
|
|
1057
|
-
}
|
|
1058
|
-
while (oldHead <= oldTail) {
|
|
1059
|
-
const item = oldItems[oldHead++];
|
|
1060
|
-
if (item !== null)
|
|
1061
|
-
this._dropItem(item);
|
|
1062
|
-
}
|
|
1063
|
-
this._items = newItems;
|
|
2237
|
+
this._items = newValues[0].$r(this, newValues, items, parent, this._end);
|
|
1064
2238
|
}
|
|
1065
2239
|
}
|
|
1066
2240
|
const rootParts = new WeakMap();
|
|
1067
2241
|
/**
|
|
1068
|
-
*
|
|
1069
|
-
*
|
|
1070
|
-
*
|
|
2242
|
+
* Writes a template result into a container. The renderer's imperative draw: no reactivity, no
|
|
2243
|
+
* lifecycle, no knowledge of components. Slots into Vera via `wire([renderer])`; core's built-in
|
|
2244
|
+
* `html` tag already produces the accepted shape, so no `setHtml` call is required — though
|
|
2245
|
+
* lit-html's `html` also works, its results being structurally identical.
|
|
2246
|
+
*
|
|
2247
|
+
* **It owns its own range and nothing else.** The first call appends a marker and anchors a root
|
|
2248
|
+
* part there; later calls with the same container reuse that part and walk only the value slots, so
|
|
2249
|
+
* nodes are updated in place rather than rebuilt. Content that was already in the container stays.
|
|
1071
2250
|
*
|
|
1072
|
-
*
|
|
2251
|
+
* **Named for the relationship, not the act.** It was `render` until 0.2.0, which collided with
|
|
2252
|
+
* core's `render` — a different function, with a different arity, that declares a *reactive*
|
|
2253
|
+
* template and commits a component's setup. Both were public and both were documented, so a reader
|
|
2254
|
+
* who knew one misread the other. `renderElement` and `renderDom` were considered and rejected: this
|
|
2255
|
+
* renders *into* a container, and the container is a `Node` — a shadow root and a fragment are both
|
|
2256
|
+
* valid, so "element" would be a lie in the type. Argument order is lit-html's on purpose.
|
|
2257
|
+
*
|
|
2258
|
+
* HYDRATION lives in `@verajs/renderer/hydrate` — a drop-in superset entry whose `renderInto` adopts
|
|
1073
2259
|
* existing server-rendered children on first render. SSR apps import from there instead of here;
|
|
1074
2260
|
* this entry carries zero hydration code.
|
|
1075
2261
|
*/
|
|
1076
|
-
const
|
|
1077
|
-
|
|
2262
|
+
const renderInto = (result, container) => {
|
|
2263
|
+
/**
|
|
2264
|
+
* The container is the argument people forget, and forgetting it failed with
|
|
2265
|
+
* `Cannot read properties of undefined (reading 'appendChild')` — a message about the internals of
|
|
2266
|
+
* a function the caller never named. Everything after this line assumes a node.
|
|
2267
|
+
*/
|
|
2268
|
+
if (true && (!container || typeof container.appendChild !== 'function'))
|
|
2269
|
+
throw new TypeError(`renderInto: expected a container node as the second argument and received ${String(container)}. ` +
|
|
2270
|
+
`It renders *into* something — \`renderInto(html\`…\`, document.body)\`.`);
|
|
2271
|
+
if (true && _profileHook)
|
|
1078
2272
|
;
|
|
1079
2273
|
let part = rootParts.get(container);
|
|
1080
2274
|
if (part === undefined) {
|
|
2275
|
+
/**
|
|
2276
|
+
* FIRST render into this container. If it is a light element host and a 'slot' insert is
|
|
2277
|
+
* wired, capture its children NOW — so slot content provided before its (possibly
|
|
2278
|
+
* conditional) `<slot>` mounts is held rather than left visible in the host, matching native
|
|
2279
|
+
* "unassigned light children do not render". Once per container lifetime; shadow roots
|
|
2280
|
+
* (nodeType 11) and fragments are excluded.
|
|
2281
|
+
*/
|
|
2282
|
+
/**
|
|
2283
|
+
* **The marker goes in FIRST, and capture is handed it as the light region's boundary.**
|
|
2284
|
+
*
|
|
2285
|
+
* This part's start marker already delimits where the render's output begins, so the boundary
|
|
2286
|
+
* slots needs is a node the renderer was creating anyway — the sentinel it used to append for
|
|
2287
|
+
* itself landed immediately before this one, two adjacent comments doing the same job. Passing
|
|
2288
|
+
* it removes one comment from every light host and keeps the two in step by construction: they
|
|
2289
|
+
* cannot drift apart if they are the same node.
|
|
2290
|
+
*
|
|
2291
|
+
* Appending before capture is safe and necessary. Safe because a comment is never a slottable,
|
|
2292
|
+
* so the children walk steps over it; necessary because capture LIFTS the host's children, and
|
|
2293
|
+
* a marker appended afterwards would land in the same place either way — this way slots has it.
|
|
2294
|
+
*/
|
|
1081
2295
|
const marker = comment();
|
|
1082
2296
|
container.appendChild(marker);
|
|
2297
|
+
if (container.nodeType === 1)
|
|
2298
|
+
slotSeam()?._$capture$?.(container, marker);
|
|
1083
2299
|
rootParts.set(container, (part = new ChildPart(marker, null)));
|
|
1084
2300
|
}
|
|
1085
|
-
|
|
1086
|
-
|
|
2301
|
+
/**
|
|
2302
|
+
* **The flush is in a `finally`, and that is not tidiness.** A render that throws after a
|
|
2303
|
+
* `<select>.value` has been queued but before the flush left the queue holding the element — which
|
|
2304
|
+
* retains it in module state, and, worse, hands the stranded value to the *next* `renderInto` call.
|
|
2305
|
+
* An unrelated component's render then silently changed a select it has nothing to do with.
|
|
2306
|
+
* Measured: a failed update left the value to be applied by the following render.
|
|
2307
|
+
*
|
|
2308
|
+
* Flushing on the way out applies it with its own pass, where it belongs, and leaves nothing
|
|
2309
|
+
* behind either way. The error still propagates.
|
|
2310
|
+
*/
|
|
2311
|
+
_slotRoot = container;
|
|
2312
|
+
try {
|
|
2313
|
+
part._set(result);
|
|
2314
|
+
}
|
|
2315
|
+
finally {
|
|
2316
|
+
_slotRoot = null;
|
|
2317
|
+
flushSelects();
|
|
2318
|
+
}
|
|
2319
|
+
if (true && _profileHook)
|
|
1087
2320
|
;
|
|
1088
2321
|
};
|
|
2322
|
+
/**
|
|
2323
|
+
* Lists, as a registered kind rather than a branch — the built-in going through the same door a
|
|
2324
|
+
* package will. Moving it to `@verajs/renderer/lists` is step 5; nothing else has to change when
|
|
2325
|
+
* it does, which is what this shape is for.
|
|
2326
|
+
*/
|
|
2327
|
+
builtIns.push((part, value) => {
|
|
2328
|
+
if (Array.isArray(value)) {
|
|
2329
|
+
part._commitList(value);
|
|
2330
|
+
return true;
|
|
2331
|
+
}
|
|
2332
|
+
if (value !== null && typeof value[Symbol.iterator] === 'function') {
|
|
2333
|
+
part._commitList([...value]);
|
|
2334
|
+
return true;
|
|
2335
|
+
}
|
|
2336
|
+
return false;
|
|
2337
|
+
});
|
|
2338
|
+
/**
|
|
2339
|
+
* Everything this renderer needs, in one entry: `wire([renderer])`.
|
|
2340
|
+
*
|
|
2341
|
+
* It registers on the `'render'` chain *and* takes the registry, because a package that both
|
|
2342
|
+
* provides a capability and reads one should not cost an app two lines. This replaced
|
|
2343
|
+
* `setRenderer`, which existed only because there was no general way to say "this app has a
|
|
2344
|
+
* renderer" — and which resolved the shadow root at registration, so a renderer wired any other
|
|
2345
|
+
* way silently rendered into the light DOM. That resolution lives in core's dispatch now.
|
|
2346
|
+
*/
|
|
2347
|
+
/**
|
|
2348
|
+
* A `true `-only hint for `wire`, so the module and the raw function beside it can share a package
|
|
2349
|
+
* without wiring the wrong one being silent.
|
|
2350
|
+
*
|
|
2351
|
+
* A bare function has no `on`, so `wire` reads it as a connector and hands it the registry. Nothing
|
|
2352
|
+
* registers, nothing throws, and the page renders nothing. The marker lets `wire` name the export
|
|
2353
|
+
* that was meant. This mattered most when the function was called `render` and the mistake was two
|
|
2354
|
+
* characters wide; `renderInto` is harder to confuse, and the guard costs nothing in production.
|
|
2355
|
+
*
|
|
2356
|
+
* `$module` is deliberately generic — any package exporting a raw function next to a module of a
|
|
2357
|
+
* similar name can set it. Production carries neither the property nor the check that reads it.
|
|
2358
|
+
*/
|
|
2359
|
+
if (true )
|
|
2360
|
+
renderInto.$module = 'renderer';
|
|
2361
|
+
const renderer = {
|
|
2362
|
+
name: '@verajs/renderer',
|
|
2363
|
+
on: 'render',
|
|
2364
|
+
fn: renderInto,
|
|
2365
|
+
priority: 50,
|
|
2366
|
+
/**
|
|
2367
|
+
* Typed against the registry `wire` actually hands over, not a narrower shape that happens to
|
|
2368
|
+
* describe the one lookup this makes. A structural `{ get(name: 'value'): … }` is **not**
|
|
2369
|
+
* assignable from `Inserts`, so `wire([renderer])` failed to compile in a consumer's project while
|
|
2370
|
+
* this repo's own typecheck — which reads sources, not the shipped `.d.ts` — saw nothing.
|
|
2371
|
+
*/
|
|
2372
|
+
connect: (given) => {
|
|
2373
|
+
registry = given;
|
|
2374
|
+
},
|
|
2375
|
+
};
|
|
1089
2376
|
|
|
1090
|
-
export { hold,
|
|
2377
|
+
export { hold, renderInto, renderer };
|
|
1091
2378
|
//# sourceMappingURL=vera-renderer.js.map
|