@proveanything/smartlinks 2.0.45 → 2.0.47

package/dist/docs/API_SUMMARY.md

@@ -1,6 +1,6 @@
 # Smartlinks API Summary
 
-Version: 2.0.45  |  Generated: 2026-10-06T17:22:34.344Z
+Version: 2.0.47  |  Generated: 2026-10-08T12:38:10.855Z
 
 This is a concise summary of all available API functions and types.
 
@@ -8300,7 +8300,7 @@ interface QueryOrdersRequest {
   itemId: string
   }>
   metadata?: Record<string, any>
-  sortBy?: string
+  sortBy?: 'createdAt' | 'updatedAt' | 'status' | 'orderRef' | 'customerId' | 'itemCount' | (string & {})
   sortOrder?: 'asc' | 'desc'
   }
   limit?: number                    // Optional: Max results (default: 100)

package/dist/docs/mobile-admin-container.md

@@ -520,9 +520,27 @@ The mobile admin bundle has its own Vite config: `vite.config.mobile-admin.ts`.
 ```
 dist/mobile-admin.umd.js
 dist/mobile-admin.esm.js
-dist/mobile-admin.css    (if needed)
+dist/mobile-admin.css    the screen's own scoped stylesheet — declare it as mobileAdmin.files.css
 ```
 
+### Styling
+
+The component renders **inside Sidekick's page**, not an iframe. Sidekick already has a CSS reset and
+its own styles, and loads your `mobileAdmin.files.css` alongside the bundle. Don't rely on Sidekick's
+classes: they only cover what Sidekick itself uses. Ship your own stylesheet, and keep it to your screen:
+
+- **No reset.** Build Tailwind's theme + utilities only (no preflight); Sidekick's reset is already there.
+- **Scoped.** Prefix every rule with a wrapper class your component renders (the example uses
+  `.sl-mobile-admin`), and turn `:root` / `html` / `body` into that wrapper, so theme variables and
+  rules can't touch Sidekick's UI.
+- **No cascade layers.** Tailwind 4 emits `@layer`; any unlayered rule on the page beats every layered
+  one, so unwrap the layers or Sidekick's own utilities win clashes inside your screen.
+
+The example app does all three with a small PostCSS step in `vite.config.mobile-admin.ts`
+(`scripts/scope-css.mjs`) over `src/mobile-admin/styles.css`, and shares its theme with the rest of the
+app through `src/tokens.css`. Forge's preview loads the same file, so the screen looks the same there as
+on a phone.
+
 ### Example `vite.config.mobile-admin.ts`
 
 ```typescript

package/dist/openapi.yaml

@@ -28332,7 +28332,8 @@ components:
           type: object
           additionalProperties: true
         sortBy:
-          type: string
+          type: object
+          additionalProperties: true
         sortOrder:
           type: string
           enum:

package/dist/types/order.d.ts

@@ -201,7 +201,12 @@ export interface QueryOrdersRequest {
             itemId: string;
         }>;
         metadata?: Record<string, any>;
-        sortBy?: string;
+        /**
+         * Sort field: `createdAt` (default), `updatedAt`, `status`, `orderRef`, `customerId` or `itemCount`
+         * (snake_case works too). Also accepts `"-updatedAt"` (descending) / `"+status"` (ascending) or
+         * `"status:asc,createdAt:desc"`. Any other field is a 400 listing the allowed ones.
+         */
+        sortBy?: 'createdAt' | 'updatedAt' | 'status' | 'orderRef' | 'customerId' | 'itemCount' | (string & {});
         sortOrder?: 'asc' | 'desc';
     };
     limit?: number;

package/docs/API_SUMMARY.md

@@ -1,6 +1,6 @@
 # Smartlinks API Summary
 
-Version: 2.0.45  |  Generated: 2026-10-06T17:22:34.344Z
+Version: 2.0.47  |  Generated: 2026-10-08T12:38:10.855Z
 
 This is a concise summary of all available API functions and types.
 
@@ -8300,7 +8300,7 @@ interface QueryOrdersRequest {
   itemId: string
   }>
   metadata?: Record<string, any>
-  sortBy?: string
+  sortBy?: 'createdAt' | 'updatedAt' | 'status' | 'orderRef' | 'customerId' | 'itemCount' | (string & {})
   sortOrder?: 'asc' | 'desc'
   }
   limit?: number                    // Optional: Max results (default: 100)

package/docs/mobile-admin-container.md

@@ -520,9 +520,27 @@ The mobile admin bundle has its own Vite config: `vite.config.mobile-admin.ts`.
 ```
 dist/mobile-admin.umd.js
 dist/mobile-admin.esm.js
-dist/mobile-admin.css    (if needed)
+dist/mobile-admin.css    the screen's own scoped stylesheet — declare it as mobileAdmin.files.css
 ```
 
+### Styling
+
+The component renders **inside Sidekick's page**, not an iframe. Sidekick already has a CSS reset and
+its own styles, and loads your `mobileAdmin.files.css` alongside the bundle. Don't rely on Sidekick's
+classes: they only cover what Sidekick itself uses. Ship your own stylesheet, and keep it to your screen:
+
+- **No reset.** Build Tailwind's theme + utilities only (no preflight); Sidekick's reset is already there.
+- **Scoped.** Prefix every rule with a wrapper class your component renders (the example uses
+  `.sl-mobile-admin`), and turn `:root` / `html` / `body` into that wrapper, so theme variables and
+  rules can't touch Sidekick's UI.
+- **No cascade layers.** Tailwind 4 emits `@layer`; any unlayered rule on the page beats every layered
+  one, so unwrap the layers or Sidekick's own utilities win clashes inside your screen.
+
+The example app does all three with a small PostCSS step in `vite.config.mobile-admin.ts`
+(`scripts/scope-css.mjs`) over `src/mobile-admin/styles.css`, and shares its theme with the rest of the
+app through `src/tokens.css`. Forge's preview loads the same file, so the screen looks the same there as
+on a phone.
+
 ### Example `vite.config.mobile-admin.ts`
 
 ```typescript

package/openapi.yaml

@@ -28332,7 +28332,8 @@ components:
           type: object
           additionalProperties: true
         sortBy:
-          type: string
+          type: object
+          additionalProperties: true
         sortOrder:
           type: string
           enum:

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@proveanything/smartlinks",
-  "version": "2.0.45",
+  "version": "2.0.47",
   "description": "Official JavaScript/TypeScript SDK for the Smartlinks API",
   "type": "module",
   "main": "dist/index.js",