@uniweb/kit 0.19.18 → 0.20.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/package.json +5 -5
- package/src/index.js +1 -1
- package/src/utils/index.js +1 -1
- package/src/utils/servicePredicates.js +11 -6
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@uniweb/kit",
|
|
3
|
-
"version": "0.
|
|
3
|
+
"version": "0.20.0",
|
|
4
4
|
"description": "Standard component library for Uniweb foundations",
|
|
5
5
|
"type": "module",
|
|
6
6
|
"exports": {
|
|
@@ -43,11 +43,11 @@
|
|
|
43
43
|
"shiki": "^3.0.0",
|
|
44
44
|
"tailwind-merge": "^3.6.0",
|
|
45
45
|
"temml": "^0.13.2",
|
|
46
|
-
"@uniweb/
|
|
46
|
+
"@uniweb/projections": "^0.7.15",
|
|
47
|
+
"@uniweb/core": "^0.38.0",
|
|
47
48
|
"@uniweb/semantic-parser": "^1.5.1",
|
|
48
|
-
"@uniweb/
|
|
49
|
-
"@uniweb/
|
|
50
|
-
"@uniweb/projections": "^0.7.14"
|
|
49
|
+
"@uniweb/schemas": "^0.13.0",
|
|
50
|
+
"@uniweb/scene": "^0.1.3"
|
|
51
51
|
},
|
|
52
52
|
"peerDependencies": {
|
|
53
53
|
"react": "^19.0.0",
|
package/src/index.js
CHANGED
package/src/utils/index.js
CHANGED
|
@@ -80,16 +80,21 @@ function activeWebsite() {
|
|
|
80
80
|
* writes? The question to ask before drawing a sign-in affordance or any
|
|
81
81
|
* control only a backend can answer.
|
|
82
82
|
*
|
|
83
|
-
* ⚠️ **`@uniweb/api` exports its OWN `
|
|
84
|
-
* one** — *this line claimed it did until 2026-09-15.* Theirs tests
|
|
83
|
+
* ⚠️ **`@uniweb/api` exports its OWN `isBackendEnabled`, it does not re-export
|
|
84
|
+
* this one** — *this line claimed it did until 2026-09-15.* Theirs tests
|
|
85
85
|
* `resolveBase(website) !== null` and takes an optional website; this one calls
|
|
86
|
-
* `isServiceEnabled('
|
|
87
|
-
* `resolveService(website, '
|
|
86
|
+
* `isServiceEnabled('backend')` on the active site. They agree — both bottom out
|
|
87
|
+
* in `resolveService(website, 'backend')`, and the input that would split them is
|
|
88
88
|
* unreachable — but they are two implementations, so a change to either is not a
|
|
89
89
|
* change to both.
|
|
90
|
+
*
|
|
91
|
+
* ⛔ **It was `isApiEnabled`, asking for the service `api`, until 2026-10-07**,
|
|
92
|
+
* when the site's own backend became the `backend` service: a service is named for
|
|
93
|
+
* what it gives the site, and `/api` is only the interface it answers on. No alias —
|
|
94
|
+
* a foundation importing the old name fails at its build, where someone will see it.
|
|
90
95
|
*/
|
|
91
|
-
export function
|
|
92
|
-
return activeWebsite()?.isServiceEnabled('
|
|
96
|
+
export function isBackendEnabled() {
|
|
97
|
+
return activeWebsite()?.isServiceEnabled('backend') ?? false
|
|
93
98
|
}
|
|
94
99
|
|
|
95
100
|
/**
|