@wix/himalaya-cli 0.1413.0 → 0.1415.0

package/dist/authoring-runtime/node_modules/@wix/himalaya/dist/_types/stdlib/wix-sdk-auto/_shared/runtime.generated.d.ts

@@ -3,6 +3,32 @@
 export interface WixCallOptions {
     site?: string;
 }
+/** The endpoint answered: `value` is what the call returns without `{ offline: "queue" }`. */
+export interface WixSent<T> {
+    status: "sent";
+    value: T;
+}
+/** The write waits in the device's offline outbox (RFC 0072); `writeId` names it in
+ *  `wixApi.offline` events. Show it as pending until `applied` or `rejected`. */
+export interface WixQueued {
+    status: "queued";
+    writeId: string;
+    tag: string;
+}
+export type WixOfflineResult<T> = WixSent<T> | WixQueued;
+/** Per-call options of a write the runtime may queue offline. `offline: "queue"` opts this ONE
+ *  call into the outbox, and the answer becomes a `WixOfflineResult<T>`. It queues only if
+ *  the app also declares a `queueOffline` cache rule for the endpoint (and, on web, the
+ *  endpoint's dedupe allows it); otherwise it is sent live as usual, and refused offline
+ *  (`err.code === "offline_write_blocked"`). */
+export interface WixQueueCallOptions extends WixCallOptions {
+    offline?: "queue";
+}
+/** What a queueable write answers for options `O`: the envelope when `O` opts in, the plain
+ *  response when it cannot, either when that is only known at runtime. */
+export type WixQueueAnswer<O, T> = O extends {
+    offline: "queue";
+} ? WixOfflineResult<T> : "offline" extends keyof O ? (O[keyof O & "offline"] extends undefined ? T : T | WixOfflineResult<T>) : T;
 /** How a request reaches the wire: the request field behind each `{…}` in the path, in
  *  order, and whether the request travels in the query string (GET/DELETE) or the body. */
 export interface WixRoute {
@@ -25,3 +51,8 @@ export interface WixRoute {
  *  Exported so the hand-written ./extensions sidecar can build the same URLs. */
 export declare function wixQueryPath(path: string, req: unknown): string;
 export declare function wixCall<T>(verb: string, template: string, req: unknown, opts?: WixCallOptions, route?: WixRoute): Promise<T>;
+/** `wixCall` for a write on the runtime's offline allow-table (RFC 0072). With
+ *  `opts.offline === "queue"` the opt-in rides as the bridge's 5th argument and the answer is
+ *  the runtime's envelope; a runtime without offline writes (no `wixApi.offline`) sends the
+ *  call live, reported as `sent`. Without it, exactly `wixCall`. */
+export declare function wixQueueCall<T, O extends WixQueueCallOptions>(verb: string, template: string, req: unknown, opts?: O, route?: WixRoute): Promise<WixQueueAnswer<O, T>>;

package/dist/authoring-runtime/node_modules/@wix/himalaya/dist/wix-comments.mjs

@@ -466,6 +466,9 @@ function withoutFields(req, fields) {
   return out;
 }
 function wixCall2(verb, template, req, opts, route = {}) {
+  return send(verb, template, req, opts, route, false);
+}
+function send(verb, template, req, opts, route, queue) {
   const api = globalThis.himalaya?.wixApi;
   if (!api) return Promise.reject(new Error("@himalaya/wix-*: host did not install the wixApi bridge"));
   const fields = route.pathFields ?? [];
@@ -485,8 +488,11 @@ function wixCall2(verb, template, req, opts, route = {}) {
   }
   const site = opts?.site?.trim();
   const headers = site ? { "wix-site-id": site } : void 0;
-  if (route.query) return api.call(verb, wixQueryPath2(path, withoutFields(req, fields)), void 0, headers);
-  return api.call(verb, path, req, headers);
+  const target = route.query ? wixQueryPath2(path, withoutFields(req, fields)) : path;
+  const body = route.query ? void 0 : req;
+  if (!queue) return api.call(verb, target, body, headers);
+  if (!api.offline) return api.call(verb, target, body, headers).then((value) => ({ status: "sent", value }));
+  return api.call(verb, target, body, headers, { offline: "queue" });
 }
 
 // ../../stdlib/wix-sdk-auto/comments/categories.generated.ts

package/dist/cli.mjs

@@ -7659,6 +7659,7 @@ function buttonVariant(style) {
 var SYSTEM_FONT_FAMILY, TONAL_ELEVATION_ALPHA, BUTTON_MIN_HIT_TARGET, nonNegative, nonEmpty, own, COLOR_TOKEN_PROPS, TYPOGRAPHY_TOKEN_PROPS, BUTTON_VARIANTS;
 var init_tokens = __esm({
   "../../core/ts/src/tokens.ts"() {
+    "use strict";
     SYSTEM_FONT_FAMILY = "$system";
     TONAL_ELEVATION_ALPHA = [0, 0.05, 0.08, 0.11, 0.12, 0.14];
     BUTTON_MIN_HIT_TARGET = 44;
@@ -7714,6 +7715,7 @@ function resolveTranslation(value, catalog3, sourceCatalog) {
 var BINDING_SIGILS, BINDING_SIGIL_RE, TRANSLATION_PREFIX, TRANSLATION_KEY_RE;
 var init_bindings = __esm({
   "../../core/ts/src/bindings.ts"() {
+    "use strict";
     BINDING_SIGILS = ["service", "flag", "item", "t"];
     BINDING_SIGIL_RE = new RegExp(
       `^\\$(?:${BINDING_SIGILS.filter((s2) => s2 !== "t").join("|")})\\b|^\\$t:`

package/guides/wix-api-usage.md

@@ -255,6 +255,15 @@ when BOTH keys turn:
 
    (`himalaya.wixApi.call(method, path, body, headers, { offline: "queue" })` is the raw form.)
 
+   A generated `@himalaya/wix-*` method takes the same option where the endpoint can queue:
+   `createRsvp(req, { offline: "queue" })` answers `WixOfflineResult<WixCreateRsvpResponse>`
+   (`sent` / `queued`, as above), and `createRsvp(req)` still answers the plain response. The
+   option (`WixQueueCallOptions`, alongside `site`) is typed only on a write whose verb and path
+   the platform lists as safe to resend, so a read or any other write rejects it at compile time.
+   Today that is `events-v2`'s `createRsvp`; the Wix Data save/insert and the cart add are
+   hand-written and take `offline.call` above. An RSVP has no server-side dedupe, so on web it
+   never queues: offline it is refused with `offline_write_blocked`.
+
 What a worker gets back:
 
 - `sent` — online and nothing of the same `tag` waiting: the endpoint's own answer.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@wix/himalaya-cli",
-  "version": "0.1413.0",
+  "version": "0.1415.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": "6678c843baa36a6bdcbf273c4b8cc253206bf27fb5b535c8b8ef5d54"
+  "falconPackageHash": "1c990236c511b70b0b5fa3ae85a7c68fd66d800cf0480250dd0acbcb"
 }