@uniweb/build 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/build",
|
|
3
|
-
"version": "1.19.
|
|
3
|
+
"version": "1.19.1",
|
|
4
4
|
"description": "Build tooling for the Uniweb Component Web Platform",
|
|
5
5
|
"type": "module",
|
|
6
6
|
"exports": {
|
|
@@ -56,15 +56,15 @@
|
|
|
56
56
|
"js-yaml": "^4.3.2",
|
|
57
57
|
"sharp": "^0.35.5",
|
|
58
58
|
"yaml": "^2.5.0",
|
|
59
|
-
"@uniweb/content-reader": "~1.5.9",
|
|
60
59
|
"@uniweb/schemas": "~1.6.11",
|
|
61
60
|
"@uniweb/semantic-parser": "~1.13.2",
|
|
62
|
-
"@uniweb/content-writer": "~1.3.1",
|
|
63
61
|
"@uniweb/theming": "~1.3.2",
|
|
64
|
-
"@uniweb/projections": "~1.2.13"
|
|
62
|
+
"@uniweb/projections": "~1.2.13",
|
|
63
|
+
"@uniweb/content-reader": "~1.5.9",
|
|
64
|
+
"@uniweb/content-writer": "~1.3.1"
|
|
65
65
|
},
|
|
66
66
|
"optionalDependencies": {
|
|
67
|
-
"@uniweb/runtime": "~1.5.
|
|
67
|
+
"@uniweb/runtime": "~1.5.4"
|
|
68
68
|
},
|
|
69
69
|
"peerDependencies": {
|
|
70
70
|
"vite": "^5.0.0 || ^6.0.0 || ^7.0.0",
|
|
@@ -73,8 +73,8 @@
|
|
|
73
73
|
"@tailwindcss/vite": "^4.0.0",
|
|
74
74
|
"@vitejs/plugin-react": "^4.0.0 || ^5.0.0",
|
|
75
75
|
"vite-plugin-svgr": "^4.0.0",
|
|
76
|
-
"@uniweb/core": "~1.6.
|
|
77
|
-
"@uniweb/runtime": "~1.5.
|
|
76
|
+
"@uniweb/core": "~1.6.9",
|
|
77
|
+
"@uniweb/runtime": "~1.5.4"
|
|
78
78
|
},
|
|
79
79
|
"peerDependenciesMeta": {
|
|
80
80
|
"vite": {
|
|
@@ -1,20 +1,14 @@
|
|
|
1
1
|
/**
|
|
2
|
-
* ⭐
|
|
3
|
-
* scope
|
|
4
|
-
*
|
|
5
|
-
*
|
|
6
|
-
* foundation and the scope's schemas package — are two definitions of one type, and whichever
|
|
7
|
-
* registers last decides what it is for the other's sites too. Copies that agree today come apart the
|
|
8
|
-
* first time one is edited.
|
|
2
|
+
* ⭐ A REGISTERED DATA SCHEMA IS USABLE BY ANY FOUNDATION OR SITE, by its full name — `@acme/member`.
|
|
3
|
+
* Its scope is a namespace, so that names never collide, and says who may publish under it, never who
|
|
4
|
+
* may use it *[Diego, 2026-09-25; 2026-11-08]*. A foundation that renders another's type declares it by
|
|
5
|
+
* that name, and a register names it and sends no definition of it (`uwx/registry-package.js`).
|
|
9
6
|
*
|
|
10
|
-
*
|
|
11
|
-
* the
|
|
12
|
-
* `
|
|
13
|
-
*
|
|
14
|
-
*
|
|
15
|
-
* `uniweb register` refuses a definition that differs from another of the same name in the workspace,
|
|
16
|
-
* since that is when a register changes what another foundation's sites read; `uniweb doctor` names
|
|
17
|
-
* every name defined twice, agreeing or not.
|
|
7
|
+
* So a copy of a type's file in a second package of the same scope is a second definition of one type,
|
|
8
|
+
* and the copies come apart the first time one is edited. `typesDefinedTwice` names each such type, for
|
|
9
|
+
* `uniweb doctor` to recommend one definition, named in full elsewhere, with `schemas.config.js`
|
|
10
|
+
* giving a local build the file (`resolve-data-schema.js`). It refuses nothing: what a register of a
|
|
11
|
+
* changed definition does is the registry's to judge.
|
|
18
12
|
*/
|
|
19
13
|
|
|
20
14
|
import { existsSync, readFileSync, realpathSync } from 'node:fs'
|