uniweb 0.14.21 → 0.14.23

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": "0.14.21",
3
+ "version": "0.14.23",
4
4
  "description": "Create structured Vite + React sites with content/code separation",
5
5
  "type": "module",
6
6
  "bin": {
@@ -41,14 +41,14 @@
41
41
  "js-yaml": "^4.1.0",
42
42
  "prompts": "^2.4.2",
43
43
  "tar": "^7.0.0",
44
- "@uniweb/kit": "0.10.18",
45
- "@uniweb/runtime": "0.9.5",
46
- "@uniweb/core": "0.8.2"
44
+ "@uniweb/core": "0.8.2",
45
+ "@uniweb/kit": "0.10.20",
46
+ "@uniweb/runtime": "0.9.6"
47
47
  },
48
48
  "peerDependencies": {
49
- "@uniweb/build": "0.16.12",
50
- "@uniweb/content-reader": "1.2.2",
51
- "@uniweb/semantic-parser": "1.2.1"
49
+ "@uniweb/build": "0.16.13",
50
+ "@uniweb/semantic-parser": "1.2.1",
51
+ "@uniweb/content-reader": "1.2.2"
52
52
  },
53
53
  "peerDependenciesMeta": {
54
54
  "@uniweb/build": {
@@ -216,6 +216,8 @@ A versionless `@org/name` is an error rather than a shorthand — the build reje
216
216
 
217
217
  > **Foundations are never npm packages.** They're runtime federated modules, not libraries. Don't `npm install` one, and don't add one to `dependencies` by hand. The four supported shapes are exactly the ones above: a workspace sibling, a `file:` dependency, a versioned registry ref, or a full URL.
218
218
 
219
+ > **The same `@scope/name` shape means different things in different places.** As a `foundation:` value it is a **catalog** ref (never npm). As a data-schema ref in `meta.js` it resolves on disk from an **npm package** — `@std/*` from `@uniweb/schemas`, any other `@org/*` from that org's `@org/schemas`. And `@uniweb/kit` in `dependencies` is an ordinary npm package. Position decides the registry; the shape tells you nothing.
220
+
219
221
  **Check `paths:` in `site.yml` before going looking for content.** It mounts outside directories into the page tree (`paths: { pages/docs: ../../../docs }`), so a route's markdown may live in another repo or a submodule rather than under `<site>/pages/`.
220
222
 
221
223
  ### 2. Learn this project's vocabulary — before you write anything
@@ -1,9 +1,9 @@
1
1
  {
2
2
  "schemaVersion": 1,
3
- "generatedAt": "2026-08-01T22:02:44.902Z",
3
+ "generatedAt": "2026-08-04T14:08:24.823Z",
4
4
  "packages": {
5
5
  "@uniweb/build": {
6
- "version": "0.16.12",
6
+ "version": "0.16.13",
7
7
  "path": "framework/build",
8
8
  "deps": [
9
9
  "@uniweb/content-reader",
@@ -45,7 +45,7 @@
45
45
  "deps": []
46
46
  },
47
47
  "@uniweb/kit": {
48
- "version": "0.10.18",
48
+ "version": "0.10.20",
49
49
  "path": "framework/kit",
50
50
  "deps": [
51
51
  "@uniweb/core",
@@ -54,7 +54,7 @@
54
54
  ]
55
55
  },
56
56
  "@uniweb/loom": {
57
- "version": "0.2.3",
57
+ "version": "0.2.4",
58
58
  "path": "framework/loom",
59
59
  "deps": []
60
60
  },
@@ -72,7 +72,7 @@
72
72
  ]
73
73
  },
74
74
  "@uniweb/runtime": {
75
- "version": "0.9.5",
75
+ "version": "0.9.6",
76
76
  "path": "framework/runtime",
77
77
  "deps": [
78
78
  "@uniweb/core",
@@ -80,7 +80,7 @@
80
80
  ]
81
81
  },
82
82
  "@uniweb/scene": {
83
- "version": "0.1.2",
83
+ "version": "0.1.3",
84
84
  "path": "framework/scene",
85
85
  "deps": []
86
86
  },
@@ -90,7 +90,7 @@
90
90
  "deps": []
91
91
  },
92
92
  "@uniweb/scholar": {
93
- "version": "0.2.2",
93
+ "version": "0.2.3",
94
94
  "path": "framework/scholar",
95
95
  "deps": []
96
96
  },
@@ -110,7 +110,7 @@
110
110
  "deps": []
111
111
  },
112
112
  "@uniweb/unipress": {
113
- "version": "0.6.10",
113
+ "version": "0.6.11",
114
114
  "path": "framework/unipress",
115
115
  "deps": [
116
116
  "@uniweb/build",