uniweb 1.0.1 → 1.0.2
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 +5 -5
- package/partials/agents.md +1 -1
- package/src/framework-index.json +3 -3
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "uniweb",
|
|
3
|
-
"version": "1.0.
|
|
3
|
+
"version": "1.0.2",
|
|
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/
|
|
45
|
-
"@uniweb/semantic-parser": "~1.5.1",
|
|
44
|
+
"@uniweb/content-writer": "~1.0.1",
|
|
46
45
|
"@uniweb/core": "~1.0.1",
|
|
47
|
-
"@uniweb/
|
|
46
|
+
"@uniweb/semantic-parser": "~1.5.1",
|
|
47
|
+
"@uniweb/schemas": "~1.0.1"
|
|
48
48
|
},
|
|
49
49
|
"peerDependencies": {
|
|
50
|
-
"@uniweb/semantic-parser": "~1.5.1",
|
|
51
50
|
"@uniweb/build": "~1.0.1",
|
|
51
|
+
"@uniweb/semantic-parser": "~1.5.1",
|
|
52
52
|
"@uniweb/content-reader": "~1.2.8"
|
|
53
53
|
},
|
|
54
54
|
"peerDependenciesMeta": {
|
package/partials/agents.md
CHANGED
|
@@ -2801,7 +2801,7 @@ npx uniweb@latest update # apply: align @uniweb/* deps AND refresh A
|
|
|
2801
2801
|
|
|
2802
2802
|
**`npx uniweb@latest update` is the command for bringing a project up to date.** It aligns the project's `@uniweb/*` dependencies *and* this AGENTS.md to the version matrix of the CLI that runs it. Deps and documentation move together — that's the whole point of the verb.
|
|
2803
2803
|
|
|
2804
|
-
**What the version numbers mean.** A patch brings fixes and features; a minor version is where Uniweb puts breaking changes — `update` lists each package that crosses one, so read those before shipping — and a major is kept for something really big. Dependencies are written as tilde ranges (`~0.
|
|
2804
|
+
**What the version numbers mean.** A patch brings fixes and features; a minor version is where Uniweb puts breaking changes — `update` lists each package that crosses one, so read those before shipping — and a major is kept for something really big. Dependencies are written as tilde ranges (`~1.0.1`), so `pnpm install` and `pnpm update` never cross a minor on their own. The move from 0.x to 1.0.1 asks nothing of a project that was on the latest 0.x versions — 1.0.1 carried every package's 0.x line over — though `update` marks each package `major · BREAKING`.
|
|
2805
2805
|
|
|
2806
2806
|
> ### ⛔ WRITE `@latest`. A BARE `uniweb update` IS USUALLY A NO-OP, AND IT SAYS SO CONVINCINGLY
|
|
2807
2807
|
>
|
package/src/framework-index.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"schemaVersion": 1,
|
|
3
|
-
"generatedAt": "2026-10-
|
|
3
|
+
"generatedAt": "2026-10-13T14:23:15.630Z",
|
|
4
4
|
"packages": {
|
|
5
5
|
"@uniweb/api": {
|
|
6
6
|
"version": "1.0.1"
|
|
@@ -36,7 +36,7 @@
|
|
|
36
36
|
"version": "1.0.1"
|
|
37
37
|
},
|
|
38
38
|
"@uniweb/runtime": {
|
|
39
|
-
"version": "1.0.
|
|
39
|
+
"version": "1.0.2"
|
|
40
40
|
},
|
|
41
41
|
"@uniweb/scene": {
|
|
42
42
|
"version": "1.0.1"
|
|
@@ -60,7 +60,7 @@
|
|
|
60
60
|
"version": "1.0.1"
|
|
61
61
|
},
|
|
62
62
|
"@uniweb/unipress": {
|
|
63
|
-
"version": "1.0.
|
|
63
|
+
"version": "1.0.2"
|
|
64
64
|
}
|
|
65
65
|
},
|
|
66
66
|
"templates": {
|