uniweb 1.19.0 → 1.19.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/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "uniweb",
3
- "version": "1.19.0",
3
+ "version": "1.19.1",
4
4
  "description": "Create structured Vite + React sites with content/code separation",
5
5
  "type": "module",
6
6
  "bin": {
@@ -42,9 +42,9 @@
42
42
  "prompts": "^2.4.2",
43
43
  "tar": "^7.0.0",
44
44
  "@uniweb/content-writer": "~1.3.0",
45
- "@uniweb/core": "~1.4.5",
46
- "@uniweb/schemas": "~1.6.5",
47
- "@uniweb/semantic-parser": "~1.13.0"
45
+ "@uniweb/core": "~1.4.6",
46
+ "@uniweb/semantic-parser": "~1.13.0",
47
+ "@uniweb/schemas": "~1.6.5"
48
48
  },
49
49
  "peerDependencies": {
50
50
  "@uniweb/build": "~1.9.0",
@@ -660,6 +660,9 @@ background: primary-900 # Palette token (bare n
660
660
  background: # Object form for more control
661
661
  image: { src: /img.jpg, position: center top }
662
662
  overlay: { enabled: true, type: dark, opacity: 0.5 }
663
+
664
+ background:
665
+ video: { src: /videos/hero.mp4, poster: /images/hero.jpg } # the poster shows until the video plays
663
666
  ```
664
667
 
665
668
  Components that render their own background declare `background: 'self'` in `meta.js`, and the runtime then draws none; to draw the author's background themselves they render kit's `<SectionBackground block={block} />`.
@@ -1874,7 +1877,7 @@ const page = website.activePage
1874
1877
  | `block.themeName` | `"light"`, `"medium"`, `"dark"` |
1875
1878
  | `block.stableId` / `block.key` | Stable ID from filename or `id:` / unique key across pages — use as React key |
1876
1879
  | `block.path` | Page route this block belongs to |
1877
- | `block.dataLoading` | True while declared data is still resolving |
1880
+ | `block.dataLoading` | True while declared data is still resolving — also on a pre-rendered page, for data the browser fetches, so the loading state is what that page first shows |
1878
1881
  | `block.dataError` | `{ <key>: message }` when the fetch filling a declared key FAILED, else `null`. A failed key is `null` in `content.data` — never `[]`, which means "no records" |
1879
1882
 
1880
1883
  ```jsx
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "schemaVersion": 1,
3
- "generatedAt": "2026-10-25T15:30:53.604Z",
3
+ "generatedAt": "2026-10-25T16:50:54.453Z",
4
4
  "packages": {
5
5
  "@uniweb/api": {
6
6
  "version": "1.6.4"
@@ -15,7 +15,7 @@
15
15
  "version": "1.3.0"
16
16
  },
17
17
  "@uniweb/core": {
18
- "version": "1.4.5"
18
+ "version": "1.4.6"
19
19
  },
20
20
  "@uniweb/frame-bridge": {
21
21
  "version": "1.0.2"
@@ -36,7 +36,7 @@
36
36
  "version": "1.2.0"
37
37
  },
38
38
  "@uniweb/runtime": {
39
- "version": "1.2.0"
39
+ "version": "1.2.1"
40
40
  },
41
41
  "@uniweb/scene": {
42
42
  "version": "1.0.1"