@wix/himalaya-cli 0.821.0 → 0.822.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/dist/cli.mjs +2 -0
- package/guides/release-notes.md +51 -0
- package/package.json +2 -2
package/dist/cli.mjs
CHANGED
|
@@ -25112,6 +25112,7 @@ function shouldRevealError(args) {
|
|
|
25112
25112
|
var EMAIL_RE, URL_HOST_RE, INTEGER_RE, NUMBER_RE;
|
|
25113
25113
|
var init_validation = __esm({
|
|
25114
25114
|
"../../core/ts/src/validation.ts"() {
|
|
25115
|
+
"use strict";
|
|
25115
25116
|
EMAIL_RE = /^[A-Za-z0-9._%+-]+@[A-Za-z0-9-]+(\.[A-Za-z0-9-]+)*\.[A-Za-z]{2,}$/;
|
|
25116
25117
|
URL_HOST_RE = /^[A-Za-z0-9-]+(\.[A-Za-z0-9-]+)*(:[0-9]+)?$/;
|
|
25117
25118
|
INTEGER_RE = /^[+-]?[0-9]+$/;
|
|
@@ -28578,6 +28579,7 @@ function validateWorkerSubtree(raw, slotId, policy, actionCatalog) {
|
|
|
28578
28579
|
var WORKER_SUBTREE_CEILINGS, ID_PART, ACTION_ID;
|
|
28579
28580
|
var init_worker_subtree = __esm({
|
|
28580
28581
|
"../../core/ts/src/worker-subtree.ts"() {
|
|
28582
|
+
"use strict";
|
|
28581
28583
|
init_worker_subtree_safe_types_generated();
|
|
28582
28584
|
WORKER_SUBTREE_CEILINGS = Object.freeze({
|
|
28583
28585
|
maxEncodedBytes: 65536,
|
package/guides/release-notes.md
CHANGED
|
@@ -14,6 +14,28 @@ areas, always in the same order, so you can skim for the one you care about.
|
|
|
14
14
|
|
|
15
15
|
---
|
|
16
16
|
|
|
17
|
+
## 2026-09-18
|
|
18
|
+
|
|
19
|
+
### Logic, data & SDKs
|
|
20
|
+
|
|
21
|
+
- **The Tier-5 guide now states the right payload for every control, and names the ones the
|
|
22
|
+
renderers disagree about.** `himi docs tier-5-add-a-screen` was wrong about three controls. It
|
|
23
|
+
now carries one table of what each control puts in the action it dispatches — the key, and that
|
|
24
|
+
it rides in `args` — followed by an explicit warning that several arms do not honour it yet:
|
|
25
|
+
web's `Toggle`, `Slider` and `SelectionControl` inject nothing, `DatePicker` differs on three
|
|
26
|
+
arms, and `Rating` ships three encodings. So a defensive reducer
|
|
27
|
+
(`String(p?.value ?? p?.text ?? "")`) is still the safe way to read a payload. The divergence is
|
|
28
|
+
documented and held from growing, not fixed — no renderer's behaviour changed. (#2462)
|
|
29
|
+
|
|
30
|
+
### Preview, push & release
|
|
31
|
+
|
|
32
|
+
- **A `.himi` package can carry your app's source, so the whole codebase travels as one file.**
|
|
33
|
+
`himi pack --dev` writes the package with the sources included, and `himi import <pkg>.himi`
|
|
34
|
+
turns it back into an editable content package — no account, no network, nothing to upload.
|
|
35
|
+
`--name` re-substitutes the app identity, so what you import is a new app rather than a second
|
|
36
|
+
copy of the one it came from. Plain `himi pack` is unchanged and still ships built output only;
|
|
37
|
+
a source-carrying package is always labelled, and the web host will not open one. (#2448)
|
|
38
|
+
|
|
17
39
|
## 2026-09-17
|
|
18
40
|
|
|
19
41
|
### Getting started & the CLI
|
|
@@ -31,6 +53,13 @@ areas, always in the same order, so you can skim for the one you care about.
|
|
|
31
53
|
editor resolves.** `himi init` scaffolds `@wix/himalaya/*`, which is the spelling `tsc` and your
|
|
32
54
|
editor resolve from the installed umbrella; the CLI accepts either and resolves both from the
|
|
33
55
|
runtime staged inside it. `himi docs wix-api-usage` carries the full mapping. (#2434)
|
|
56
|
+
- **`himi cms create` was refusing collection ids that Wix accepts.** The cap was enforced at 36
|
|
57
|
+
characters, and the real limit on `DataCollection.id` is 256 — so a descriptive id came back
|
|
58
|
+
rejected with nothing actually wrong with it. (#2447)
|
|
59
|
+
- **Wix member login now completes with an `https` redirect URI.** The callback was recognised by
|
|
60
|
+
comparing only the redirect URI's *scheme*, which happens to be exact for a native custom scheme
|
|
61
|
+
and far too loose for every `https://` one — so the token exchange ran against a URL that was not
|
|
62
|
+
the callback and the sign-in never finished. (#2452)
|
|
34
63
|
|
|
35
64
|
### Validate & test
|
|
36
65
|
|
|
@@ -49,6 +78,20 @@ areas, always in the same order, so you can skim for the one you care about.
|
|
|
49
78
|
that URL refused the app with nothing explaining why. The warning names the key, the consequence
|
|
50
79
|
and the fix — and never fails `--strict`, because a phone-only app is a legitimate app. The
|
|
51
80
|
authoring preview `/preview/a/<app>` was never gated by that flag and renders either way. (#2432)
|
|
81
|
+
- **`himi pull --force` now names the files it kept, and `--replace` removes them instead.**
|
|
82
|
+
`--force` wrote the archive over a non-empty directory and left anything the release did not
|
|
83
|
+
carry silently in place, so you could end up holding — and pushing — a tree that matched no
|
|
84
|
+
release you ever published. Those files are now reported as `left: [...]`, and `--replace`
|
|
85
|
+
removes them first and reports `removed: [...]`. Both consider only the paths a push would have
|
|
86
|
+
archived, so your `.git`, `node_modules`, `dist` and `.env*` are out of reach by construction —
|
|
87
|
+
and out of the report. `--replace` refuses a directory holding no `himalaya.content.json`, so a
|
|
88
|
+
mistyped `--out` cannot clear an unrelated tree, and an archive carrying a path today's rules
|
|
89
|
+
refuse is reported as `refused` rather than written. (#2444)
|
|
90
|
+
- **A push too large to be accepted now fails locally, naming the size.** `himi push` sends your
|
|
91
|
+
bundles, assets, icon and source archive in one request, so two artifacts that each passed their
|
|
92
|
+
own limit could still exceed the request limit together — and the answer was a bare `413` with
|
|
93
|
+
nothing in it to act on. The refusal now names the measured body size, the limit, and
|
|
94
|
+
`--no-source`. (#2449)
|
|
52
95
|
|
|
53
96
|
### Shipping binaries
|
|
54
97
|
|
|
@@ -59,6 +102,14 @@ areas, always in the same order, so you can skim for the one you care about.
|
|
|
59
102
|
colour. `book` and `graduation` are new, so an education app has a mark of its own, and
|
|
60
103
|
`himi icon glyphs` names the default. (#2431)
|
|
61
104
|
|
|
105
|
+
### Branded Lite & Owner Lite
|
|
106
|
+
|
|
107
|
+
- **Owner Lite can hold several Wix businesses open at once.** Site scope was process-wide, so an
|
|
108
|
+
owner with three restaurants could only ever look at one of them, and "which of my businesses
|
|
109
|
+
needs me right now" was not a question the app could answer. A per-call site now moves the signed
|
|
110
|
+
credential rather than only the request header, so asking for another business no longer answers
|
|
111
|
+
`403` with nothing to explain it. (#2460)
|
|
112
|
+
|
|
62
113
|
## 2026-09-16
|
|
63
114
|
|
|
64
115
|
### Authoring screens
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@wix/himalaya-cli",
|
|
3
|
-
"version": "0.
|
|
3
|
+
"version": "0.822.0",
|
|
4
4
|
"type": "module",
|
|
5
5
|
"description": "himi — the Himalaya authoring CLI. Build a Tier-5 content package on your own machine, push it to the production serve as a draft, preview it on web + Himi Player, and read worker logs back — the remote dev loop. Wraps @himalaya/serve-cli for transport.",
|
|
6
6
|
"keywords": [
|
|
@@ -63,5 +63,5 @@
|
|
|
63
63
|
"artifactId": "himalaya-cli"
|
|
64
64
|
}
|
|
65
65
|
},
|
|
66
|
-
"falconPackageHash": "
|
|
66
|
+
"falconPackageHash": "7c2d068c0d6e24b5c57701a69b820866c5307d58348ea185ca243d74"
|
|
67
67
|
}
|