@pylonsync/sdk 0.3.30 → 0.3.31

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.
Files changed (2) hide show
  1. package/package.json +1 -1
  2. package/src/studio.ts +16 -0
package/package.json CHANGED
@@ -3,7 +3,7 @@
3
3
  "publishConfig": {
4
4
  "access": "public"
5
5
  },
6
- "version": "0.3.30",
6
+ "version": "0.3.31",
7
7
  "type": "module",
8
8
  "main": "src/index.ts",
9
9
  "types": "src/index.ts",
package/src/studio.ts CHANGED
@@ -349,6 +349,22 @@ export interface StudioConfig {
349
349
  * present in the project, so users rarely set it explicitly.
350
350
  */
351
351
  hasExtensions?: boolean;
352
+ /**
353
+ * URL to send unauthenticated callers to when they hit `/studio`.
354
+ * Lets a host app (Pylon Cloud, an enterprise dashboard) point the
355
+ * Studio gate at its own email/password login page instead of the
356
+ * built-in `/studio/login` admin-token form.
357
+ *
358
+ * The framework appends `?next=/studio` so the host app can redirect
359
+ * back after sign-in. Authenticated-but-not-admin users still see
360
+ * the framework's "access denied" page (no point sending them back
361
+ * to a login they're already past).
362
+ *
363
+ * Example: `loginUrl: "/login"` — cloud.pylonsync.com handles `/login`
364
+ * at the dashboard, and the user's existing session cookie lifts
365
+ * them to admin via `auth.user.adminField` on the way back.
366
+ */
367
+ loginUrl?: string;
352
368
  }
353
369
 
354
370
  /**