@verajs/renderer 0.2.2 → 0.3.0
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 +711 -225
- package/dist/development/vera-renderer-elements.d.ts +39 -0
- package/dist/development/vera-renderer-elements.d.ts.map +1 -0
- package/dist/development/vera-renderer-elements.js +193 -0
- package/dist/development/vera-renderer-elements.js.map +1 -0
- package/dist/development/vera-renderer-hydrate-slots.d.ts +94 -0
- package/dist/development/vera-renderer-hydrate-slots.d.ts.map +1 -0
- package/dist/development/vera-renderer-hydrate-slots.js +325 -0
- package/dist/development/vera-renderer-hydrate-slots.js.map +1 -0
- package/dist/development/vera-renderer-hydration.d.ts +332 -0
- package/dist/development/vera-renderer-hydration.d.ts.map +1 -0
- package/dist/development/vera-renderer-hydration.js +864 -0
- package/dist/development/vera-renderer-hydration.js.map +1 -0
- package/dist/development/vera-renderer-keyed.d.ts +25 -8
- package/dist/development/vera-renderer-keyed.d.ts.map +1 -1
- package/dist/development/vera-renderer-keyed.js +843 -268
- package/dist/development/vera-renderer-keyed.js.map +1 -1
- package/dist/development/vera-renderer-multi-window.d.ts +5 -0
- package/dist/development/vera-renderer-multi-window.d.ts.map +1 -0
- package/dist/development/vera-renderer-multi-window.js +40 -0
- package/dist/development/vera-renderer-multi-window.js.map +1 -0
- package/dist/development/vera-renderer-namespaces.d.ts +64 -0
- package/dist/development/vera-renderer-namespaces.d.ts.map +1 -0
- package/dist/development/vera-renderer-namespaces.js +94 -0
- package/dist/development/vera-renderer-namespaces.js.map +1 -0
- package/dist/development/vera-renderer-native-elements.d.ts +13 -0
- package/dist/development/vera-renderer-native-elements.d.ts.map +1 -0
- package/dist/development/vera-renderer-native-elements.js +231 -0
- package/dist/development/vera-renderer-native-elements.js.map +1 -0
- package/dist/development/vera-renderer-portal.d.ts +29 -0
- package/dist/development/vera-renderer-portal.d.ts.map +1 -0
- package/dist/development/vera-renderer-portal.js +167 -0
- package/dist/development/vera-renderer-portal.js.map +1 -0
- package/dist/development/vera-renderer-profiler.d.ts +48 -96
- package/dist/development/vera-renderer-profiler.d.ts.map +1 -1
- package/dist/development/vera-renderer-profiler.js +2423 -2140
- package/dist/development/vera-renderer-profiler.js.map +1 -1
- package/dist/development/vera-renderer-slots.d.ts +88 -92
- package/dist/development/vera-renderer-slots.d.ts.map +1 -1
- package/dist/development/vera-renderer-slots.js +1834 -1237
- package/dist/development/vera-renderer-slots.js.map +1 -1
- package/dist/development/vera-renderer-spread.d.ts +7 -41
- package/dist/development/vera-renderer-spread.d.ts.map +1 -1
- package/dist/development/vera-renderer-spread.js +539 -477
- package/dist/development/vera-renderer-spread.js.map +1 -1
- package/dist/development/vera-renderer-tag.d.ts +12 -3
- package/dist/development/vera-renderer-tag.d.ts.map +1 -1
- package/dist/development/vera-renderer-tag.js +671 -513
- package/dist/development/vera-renderer-tag.js.map +1 -1
- package/dist/development/vera-renderer-until.d.ts +24 -0
- package/dist/development/vera-renderer-until.d.ts.map +1 -0
- package/dist/development/vera-renderer-until.js +83 -0
- package/dist/development/vera-renderer-until.js.map +1 -0
- package/dist/development/vera-renderer.d.ts +48 -96
- package/dist/development/vera-renderer.d.ts.map +1 -1
- package/dist/development/vera-renderer.js +2400 -2104
- package/dist/development/vera-renderer.js.map +1 -1
- package/dist/vera-renderer-elements.min.js +2 -0
- package/dist/vera-renderer-elements.min.js.map +1 -0
- package/dist/vera-renderer-hydrate-slots.min.js +2 -0
- package/dist/vera-renderer-hydrate-slots.min.js.map +1 -0
- package/dist/vera-renderer-hydration.min.js +3 -0
- package/dist/vera-renderer-hydration.min.js.map +1 -0
- package/dist/vera-renderer-keyed.min.js +1 -1
- package/dist/vera-renderer-keyed.min.js.map +1 -1
- package/dist/vera-renderer-multi-window.min.js +2 -0
- package/dist/vera-renderer-multi-window.min.js.map +1 -0
- package/dist/vera-renderer-namespaces.min.js +2 -0
- package/dist/vera-renderer-namespaces.min.js.map +1 -0
- package/dist/vera-renderer-native-elements.min.js +2 -0
- package/dist/vera-renderer-native-elements.min.js.map +1 -0
- package/dist/vera-renderer-portal.min.js +2 -0
- package/dist/vera-renderer-portal.min.js.map +1 -0
- package/dist/vera-renderer-slots.min.js +1 -1
- package/dist/vera-renderer-slots.min.js.map +1 -1
- package/dist/vera-renderer-spread.min.js +1 -1
- package/dist/vera-renderer-spread.min.js.map +1 -1
- package/dist/vera-renderer-tag.min.js +1 -1
- package/dist/vera-renderer-tag.min.js.map +1 -1
- package/dist/vera-renderer-until.min.js +2 -0
- package/dist/vera-renderer-until.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 +52 -9
- package/dist/development/vera-renderer-hydrate.d.ts +0 -147
- package/dist/development/vera-renderer-hydrate.d.ts.map +0 -1
- package/dist/development/vera-renderer-hydrate.js +0 -3136
- package/dist/development/vera-renderer-hydrate.js.map +0 -1
- package/dist/vera-renderer-hydrate.min.js +0 -2
- package/dist/vera-renderer-hydrate.min.js.map +0 -1
|
@@ -1,53 +1,19 @@
|
|
|
1
|
-
/**
|
|
2
|
-
* Branded rather than duck-typed: the element position already means "element ref", and a props bag
|
|
3
|
-
* is indistinguishable from a ref object — `{ value: 5 }` is legitimately either.
|
|
4
|
-
*/
|
|
5
|
-
/** The branded, self-applying result — what the renderer's element position recognises. */
|
|
1
|
+
/** The branded, self-applying result — what the renderer's element position recognizes. */
|
|
6
2
|
type SpreadResult = {
|
|
7
3
|
_props: Record<string, unknown>;
|
|
8
4
|
_$apply$: unknown;
|
|
9
5
|
_$attrs$: unknown;
|
|
10
6
|
};
|
|
11
7
|
/**
|
|
12
|
-
* `
|
|
13
|
-
*
|
|
14
|
-
* an INTERFACE does not, so `spread(myProps)` was a TS2345 for every user who declared their props
|
|
15
|
-
* the way the TypeScript handbook teaches — while the sibling `props()` accepted the same value,
|
|
16
|
-
* because it is generic. Two functions in one module disagreeing about a user's own type is the
|
|
17
|
-
* kind of thing nobody reports as a bug; they just stop using the one that refused them.
|
|
8
|
+
* Binds every key of `props` to the element it is placed on. Keys follow the template sigils — `.prop`,
|
|
9
|
+
* `?bool`, `@event` (or `onClick`), `&ref`, `!live` — and a plain key is an attribute.
|
|
18
10
|
*
|
|
19
|
-
*
|
|
20
|
-
*
|
|
21
|
-
*
|
|
22
|
-
* runtime deliberately tolerates.
|
|
11
|
+
* Already-branded input is returned as-is (JSX compiles `{...spread(x)}` to a spread of a spread). A
|
|
12
|
+
* value that is not a plain object is refused in BOTH builds — a string would otherwise be iterated by
|
|
13
|
+
* character index into attributes named `0`, `1`, `2` — and development says so.
|
|
23
14
|
*/
|
|
24
15
|
declare const spread: (props: object | null | undefined) => SpreadResult;
|
|
25
|
-
/**
|
|
26
|
-
* A bag of PROPERTY bindings — the object form of `.name=${value}`, one call in both surfaces:
|
|
27
|
-
*
|
|
28
|
-
* ```js
|
|
29
|
-
* html`<calendar-day ${props({ date, events })}></calendar-day>`
|
|
30
|
-
* ```
|
|
31
|
-
* ```jsx
|
|
32
|
-
* <calendar-day {...props({ date, events })}></calendar-day>
|
|
33
|
-
* ```
|
|
34
|
-
*
|
|
35
|
-
* Exists because an attribute is always a string: an array, a `Date` or a store can only reach a
|
|
36
|
-
* custom element as a property — vera's JSX accepts the sigil spelling, TSX's type-checker refuses
|
|
37
|
-
* it (`TS1003`), and this bag is the typed path either way. Every key is a
|
|
38
|
-
* property NAME, never a sigil — `props({ date })` binds `.date`, so `props({ '.date': d })` would
|
|
39
|
-
* bind `..date` and is the caller's mistake to keep.
|
|
40
|
-
*
|
|
41
|
-
* Properties only, by definition: events and boolean attributes keep their own spellings
|
|
42
|
-
* (`@click`/`onClick`, `?disabled`). **Prefer keys spelled conditionally over bags that change
|
|
43
|
-
* shape** — `props({ date: loaded ? date : null })` over `props(loaded ? { date } : {})`. Both
|
|
44
|
-
* work: a key appearing later on a component goes through `_$adopt$` and arrives reactive, and a
|
|
45
|
-
* key that disappears restores what the element held — but a stable shape updates in place, the
|
|
46
|
-
* same reason templates prefer `?hidden` over swapped subtrees.
|
|
47
|
-
*
|
|
48
|
-
* With an explicit type argument the bag is checked against the element —
|
|
49
|
-
* `props<CalendarDay>({ dat })` is a compile error naming the misspelling.
|
|
50
|
-
*/
|
|
16
|
+
/** Every key as a property: `props({ items })` is `spread({ '.items': items })` — how a component receives data. */
|
|
51
17
|
declare const props: <T extends object = Record<string, unknown>>(values: Partial<T>) => SpreadResult;
|
|
52
18
|
|
|
53
19
|
export { props, spread };
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"version":3,"file":"vera-renderer-spread.d.ts","sources":["../../src/spread.ts"],"mappings":"AAAA
|
|
1
|
+
{"version":3,"file":"vera-renderer-spread.d.ts","sources":["../../src/spread.ts"],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;","names":[]}
|