@wix/himalaya-cli 0.1538.0 → 0.1540.0

package/guides/search-list.service.ts

@@ -95,7 +95,11 @@ function shape(s: Partial<PostsState>): PostsState {
 // under `himi test` / `himi render`.
 const STATUS = /\b(?:HTTP|Wix) (\d{3})\b/;
 // No answer at all — what a dropped connection says on every platform.
-const TRANSPORT = /NSURLErrorDomain|(?:UnknownHost|Connect|SocketTimeout|NoRouteToHost|SSLHandshake)Exception|Failed to connect|Unable to resolve host|Connection (?:refused|reset)|Network is unreachable|Software caused connection abort|ECONNRESET|ETIMEDOUT|EPIPE|Broken pipe|stream was reset|unexpected end of stream|timed out|^timeout$|Failed to fetch|NetworkError|^(?:TypeError: )?Load failed$|net::ERR_|^[a-z0-9-]+(?:\.[a-z0-9-]+)+$/i;
+const TRANSPORT = /(?:UnknownHost|Connect|NoRouteToHost|SSLHandshake)Exception|Unable to resolve host|Connection (?:refused|reset)|Network is unreachable|Software caused connection abort|ECONNRESET|EPIPE|Broken pipe|stream was reset|unexpected end of stream|Failed to fetch|NetworkError|^(?:TypeError: )?Load failed$|net::ERR_|^[a-z0-9-]+(?:\.[a-z0-9-]+)+$/i;
+// iOS reports a URLError as `NSURLErrorDomain error <code>`: only the no-route codes are offline. A bad server
+// response (-1011) or a timeout is a server problem, as in the SDK's classifyLoadError.
+const URL_ERROR = /NSURLErrorDomain\D*?(-?\d{3,5})/;
+const URL_OFFLINE = new Set([-1009, -1005, -1004, -1003, -1006, -1020]);
 // Android reports an unknown host as the bare hostname (`users.wix.com`) — hence the last form.
 // No session on the device: the native bridge refuses before any request leaves.
 // A pinned site with no member session: iOS `siteNotPermitted(requested: "account", …)`,
@@ -127,6 +131,8 @@ function classifyError(e: unknown, authState: "signedIn" | "signedOut" | "unknow
     ? /"detail"\s*:\s*"([^"]+)"/.exec(msg)?.[1] ?? msg
     : msg;
   if (status && detail === msg) return "server";
+  const urlCode = URL_ERROR.exec(detail)?.[1];
+  if (urlCode !== undefined) return URL_OFFLINE.has(Number(urlCode)) ? "offline" : "server";
   if (TRANSPORT.test(detail)) return "offline";
   return "server";   // anything else — a bug, a malformed row — is not the user's connection
 }

package/guides/templates.md

@@ -143,6 +143,25 @@ preview — the `clientId` **is** the site binding (no separate MSID field). Pla
 `YOUR_WIX_CLIENT_ID` are not a real backend. Monorepo / native binary path:
 [branded-lite-site-binding.md](branded-lite-site-binding.md).
 
+### Keep the copied `_shared` helpers current
+
+`init` copies the platform helpers under `tier5-src/_shared/` once, and nothing updates them. An old
+copy keeps compiling against a newer platform and can break a feature without an error (an old
+`iap-presentation.ts` left a Buy button disabled). So every build compares each copy with the ones
+the running CLI ships. `himi build` lists a mismatch under `warnings`; `validate`, `push` and `pack`
+report it as one issue (`pass: "stale-shared"`, `ruleCode: "shared-file-differs"`, `files: [{path,
+shipped, alsoCopy}]`) with severity `warning`, which `--strict` does not promote. (`push --only`
+lists it under `warnings`; `template publish` runs the same lint but prints issues only when it
+refuses.) The message names each file and prints
+the command that refreshes it, plus any `_shared` file the shipped copy imports that your package
+lacks. A copy that matches any template's variant counts as current; the refresh takes the variant of
+the template `init` recorded in `.himi/init-source.json`, or else the one closest to your copy. Files
+the CLI does not ship are yours and are not checked.
+
+When you changed a helper on purpose, add a `// himi:forked` line to it and the check skips that
+file; `himi template sweep` adds that line to any `_shared` file it rewrites. Nothing else records
+which files you edited after `init`, so an unmarked edit and an old copy look the same.
+
 ## Publish your own
 
 Any himi app can *become* a template. Add a `himalaya.template.json` next to

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@wix/himalaya-cli",
-  "version": "0.1538.0",
+  "version": "0.1540.0",
   "type": "module",
   "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.",
   "keywords": [
@@ -71,5 +71,5 @@
       "artifactId": "himalaya-cli"
     }
   },
-  "falconPackageHash": "a1a15dbe939dfa2c63ef1cc4b38f88d026f5eda14efaf885d5c9aa84"
+  "falconPackageHash": "a1d4dc831a852d303dab5ab6d7d7c2eea37f28a6f0c949a4d2c1ce6f"
 }

package/stdlib/design-kits/dark-luxe.json

@@ -32,6 +32,10 @@
         "light": "#101319",
         "dark": "#101319"
       },
+      "surfaceTertiary": {
+        "light": "#232834",
+        "dark": "#232834"
+      },
       "textPrimary": {
         "light": "#F1E9D2",
         "dark": "#F1E9D2"