zitejs 0.9.116 → 0.9.118

package/dist/cjs/bundle/index.js

@@ -96,6 +96,12 @@ const PREBUNDLED_LIBS = {
     '@elevenlabs/elevenlabs-js': '__elevenlabs__.js',
     'resend': '__resend__.js',
     '@clickhouse/client-web': '__clickhouse__.js',
+    // Three packages, one module: the presigners take an S3Client instance, so a
+    // separate bundle each would hand them a structurally identical but distinct
+    // class. The worker bundles all three together for that reason.
+    '@aws-sdk/client-s3': '__aws-s3__.js',
+    '@aws-sdk/s3-request-presigner': '__aws-s3__.js',
+    '@aws-sdk/s3-presigned-post': '__aws-s3__.js',
 };
 exports.BASE_BUILD_OPTIONS = {
     bundle: true,

package/dist/cjs/runtime/index.d.ts

@@ -332,6 +332,5 @@ export interface EmailClient {
  * app's connected email integration key.
  */
 export declare function createEmailClient(integrationId: string): EmailClient;
-export type { NotificationLink, NotificationsCreateParams, NotificationsCreateResult, } from "../notifications/index.js";
 export { createCaller } from "../caller/index.js";
 export type { EndpointConfig } from "../caller/index.js";

package/dist/cjs/sync/lib.js

@@ -412,26 +412,6 @@ function generateSchema(database, existingSchema) {
 }
 function generateSentinelSdkTypes() {
     return [
-        "export interface NotificationLink {",
-        "  path?: string;",
-        "  params?: Record<string, string>;",
-        "}",
-        "",
-        "export interface NotificationsCreateParams {",
-        "  recipients: string[];",
-        "  title: string;",
-        "  body?: string;",
-        "  link?: NotificationLink;",
-        "  path?: string;",
-        "  params?: Record<string, string>;",
-        "  payload?: Record<string, unknown>;",
-        "  idempotencyKey?: string;",
-        "}",
-        "",
-        "export type NotificationsCreateResult =",
-        "  | { created: number }",
-        "  | { created: 0; preview: true; wouldCreate: number };",
-        "",
         // Must match `AuthUser` in zitejs/runtime and `User` in zitejs/auth.
         "export interface ZiteAuthUser {",
         "  id: string;",
@@ -638,10 +618,6 @@ function generateDbTs(inputSchema) {
             (table.name ? ` // "${commentSafe(table.name)}"` : ""));
     }
     lines.push(`  sql: createSqlClient(),`);
-    // No `notifications` here: it is a platform primitive, not something backed
-    // by the project database, so it lives at `zitejs/notifications` alongside
-    // `zitejs/pdf` and `zitejs/schedules`. Keeping it on `zite` cost a table
-    // named "Notifications" its accessor — see RESERVED_TABLE_ACCESSORS.
     lines.push(`  auth: createAuthClient<ZiteAuthUser>(),`);
     lines.push("};");
     lines.push("");

package/dist/cjs/sync/sdkNames.d.ts

@@ -41,9 +41,9 @@ export declare function toSdkName(name: string): string;
  * `notifications` used to be here and no longer is: it was a platform
  * primitive hanging off `zite`, so a table named "Notifications" collided with
  * it and — because the sentinel was written last — lost its client entirely.
- * Moving it to `zitejs/notifications` removes the collision rather than
- * managing it, and frees the name for the table that wants it. Everything left
- * is genuinely backed by the project database.
+ * The platform client is unpublished for now, which removes the collision
+ * rather than managing it, and frees the name for the table that wants it.
+ * Everything left is genuinely backed by the project database.
  */
 export declare const RESERVED_TABLE_ACCESSORS: readonly ["sql", "auth"];
 /**

package/dist/cjs/sync/sdkNames.js

@@ -86,9 +86,9 @@ function toSdkName(name) {
  * `notifications` used to be here and no longer is: it was a platform
  * primitive hanging off `zite`, so a table named "Notifications" collided with
  * it and — because the sentinel was written last — lost its client entirely.
- * Moving it to `zitejs/notifications` removes the collision rather than
- * managing it, and frees the name for the table that wants it. Everything left
- * is genuinely backed by the project database.
+ * The platform client is unpublished for now, which removes the collision
+ * rather than managing it, and frees the name for the table that wants it.
+ * Everything left is genuinely backed by the project database.
  */
 exports.RESERVED_TABLE_ACCESSORS = ["sql", "auth"];
 /**

package/dist/cjs/sync/sdkNames.test.js

@@ -35,8 +35,8 @@ const recordTypeKeys = (source, typeName) => {
     // Sudzy Dashboard: a table named "Notifications" emitted a second
     // `notifications:` key and the platform client — written last — won, so the
     // table lost findAll and typed as `{ create(NotificationsCreateParams) }`.
-    // The platform client has since moved to `zitejs/notifications`, so the name
-    // belongs to the table again and there is nothing left to collide with.
+    // The platform client is unpublished, so the name belongs to the table
+    // again and there is nothing left to collide with.
     (0, vitest_1.it)("lets a table keep the notifications accessor", () => {
         const schema = (0, lib_js_1.generateSchema)(database([{ id: "tbl_1", name: "Notifications", fields: [] }]));
         (0, vitest_1.expect)(schema.tables[0].sdkName).toBe("notifications");
@@ -194,8 +194,8 @@ const recordTypeKeys = (source, typeName) => {
     // the only thing standing between it and a TS1117 it cannot build past.
     (0, vitest_1.it)("repairs a committed schema that already holds the collision", () => {
         // `sql`, not `notifications` — the latter stopped being a platform
-        // accessor when the client moved to `zitejs/notifications`, so a schema
-        // holding it is no longer a collision to repair.
+        // accessor when the client was unpublished, so a schema holding it is
+        // no longer a collision to repair.
         const source = (0, lib_js_1.generateDbTs)({
             tables: [
                 { id: "tbl_1", sdkName: "sql", fields: [] },

package/dist/esm/bundle/index.js

@@ -59,6 +59,12 @@ const PREBUNDLED_LIBS = {
     '@elevenlabs/elevenlabs-js': '__elevenlabs__.js',
     'resend': '__resend__.js',
     '@clickhouse/client-web': '__clickhouse__.js',
+    // Three packages, one module: the presigners take an S3Client instance, so a
+    // separate bundle each would hand them a structurally identical but distinct
+    // class. The worker bundles all three together for that reason.
+    '@aws-sdk/client-s3': '__aws-s3__.js',
+    '@aws-sdk/s3-request-presigner': '__aws-s3__.js',
+    '@aws-sdk/s3-presigned-post': '__aws-s3__.js',
 };
 export const BASE_BUILD_OPTIONS = {
     bundle: true,

package/dist/esm/runtime/index.d.ts

@@ -332,6 +332,5 @@ export interface EmailClient {
  * app's connected email integration key.
  */
 export declare function createEmailClient(integrationId: string): EmailClient;
-export type { NotificationLink, NotificationsCreateParams, NotificationsCreateResult, } from "../notifications/index.js";
 export { createCaller } from "../caller/index.js";
 export type { EndpointConfig } from "../caller/index.js";

package/dist/esm/sync/lib.js

@@ -399,26 +399,6 @@ export function generateSchema(database, existingSchema) {
 }
 function generateSentinelSdkTypes() {
     return [
-        "export interface NotificationLink {",
-        "  path?: string;",
-        "  params?: Record<string, string>;",
-        "}",
-        "",
-        "export interface NotificationsCreateParams {",
-        "  recipients: string[];",
-        "  title: string;",
-        "  body?: string;",
-        "  link?: NotificationLink;",
-        "  path?: string;",
-        "  params?: Record<string, string>;",
-        "  payload?: Record<string, unknown>;",
-        "  idempotencyKey?: string;",
-        "}",
-        "",
-        "export type NotificationsCreateResult =",
-        "  | { created: number }",
-        "  | { created: 0; preview: true; wouldCreate: number };",
-        "",
         // Must match `AuthUser` in zitejs/runtime and `User` in zitejs/auth.
         "export interface ZiteAuthUser {",
         "  id: string;",
@@ -625,10 +605,6 @@ export function generateDbTs(inputSchema) {
             (table.name ? ` // "${commentSafe(table.name)}"` : ""));
     }
     lines.push(`  sql: createSqlClient(),`);
-    // No `notifications` here: it is a platform primitive, not something backed
-    // by the project database, so it lives at `zitejs/notifications` alongside
-    // `zitejs/pdf` and `zitejs/schedules`. Keeping it on `zite` cost a table
-    // named "Notifications" its accessor — see RESERVED_TABLE_ACCESSORS.
     lines.push(`  auth: createAuthClient<ZiteAuthUser>(),`);
     lines.push("};");
     lines.push("");

package/dist/esm/sync/sdkNames.d.ts

@@ -41,9 +41,9 @@ export declare function toSdkName(name: string): string;
  * `notifications` used to be here and no longer is: it was a platform
  * primitive hanging off `zite`, so a table named "Notifications" collided with
  * it and — because the sentinel was written last — lost its client entirely.
- * Moving it to `zitejs/notifications` removes the collision rather than
- * managing it, and frees the name for the table that wants it. Everything left
- * is genuinely backed by the project database.
+ * The platform client is unpublished for now, which removes the collision
+ * rather than managing it, and frees the name for the table that wants it.
+ * Everything left is genuinely backed by the project database.
  */
 export declare const RESERVED_TABLE_ACCESSORS: readonly ["sql", "auth"];
 /**

package/dist/esm/sync/sdkNames.js

@@ -76,9 +76,9 @@ export function toSdkName(name) {
  * `notifications` used to be here and no longer is: it was a platform
  * primitive hanging off `zite`, so a table named "Notifications" collided with
  * it and — because the sentinel was written last — lost its client entirely.
- * Moving it to `zitejs/notifications` removes the collision rather than
- * managing it, and frees the name for the table that wants it. Everything left
- * is genuinely backed by the project database.
+ * The platform client is unpublished for now, which removes the collision
+ * rather than managing it, and frees the name for the table that wants it.
+ * Everything left is genuinely backed by the project database.
  */
 export const RESERVED_TABLE_ACCESSORS = ["sql", "auth"];
 /**

package/dist/esm/sync/sdkNames.test.js

@@ -33,8 +33,8 @@ describe("reserved platform accessors", () => {
     // Sudzy Dashboard: a table named "Notifications" emitted a second
     // `notifications:` key and the platform client — written last — won, so the
     // table lost findAll and typed as `{ create(NotificationsCreateParams) }`.
-    // The platform client has since moved to `zitejs/notifications`, so the name
-    // belongs to the table again and there is nothing left to collide with.
+    // The platform client is unpublished, so the name belongs to the table
+    // again and there is nothing left to collide with.
     it("lets a table keep the notifications accessor", () => {
         const schema = generateSchema(database([{ id: "tbl_1", name: "Notifications", fields: [] }]));
         expect(schema.tables[0].sdkName).toBe("notifications");
@@ -192,8 +192,8 @@ describe("normalizeSchemaNames", () => {
     // the only thing standing between it and a TS1117 it cannot build past.
     it("repairs a committed schema that already holds the collision", () => {
         // `sql`, not `notifications` — the latter stopped being a platform
-        // accessor when the client moved to `zitejs/notifications`, so a schema
-        // holding it is no longer a collision to repair.
+        // accessor when the client was unpublished, so a schema holding it is
+        // no longer a collision to repair.
         const source = generateDbTs({
             tables: [
                 { id: "tbl_1", sdkName: "sql", fields: [] },

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "zitejs",
-  "version": "0.9.116",
-  "description": "The Zite framework \u2014 build apps on Zite Database",
+  "version": "0.9.118",
+  "description": "The Zite framework — build apps on Zite Database",
   "type": "module",
   "main": "./dist/cjs/index.js",
   "module": "./dist/esm/index.js",
@@ -74,11 +74,6 @@
       "import": "./dist/esm/schedules/index.js",
       "require": "./dist/cjs/schedules/index.js"
     },
-    "./notifications": {
-      "types": "./dist/esm/notifications/index.d.ts",
-      "import": "./dist/esm/notifications/index.js",
-      "require": "./dist/cjs/notifications/index.js"
-    },
     "./sync": {
       "types": "./dist/esm/sync/index.d.ts",
       "import": "./dist/esm/sync/index.js",
@@ -136,9 +131,6 @@
       "schedules": [
         "dist/esm/schedules/index.d.ts"
       ],
-      "notifications": [
-        "dist/esm/notifications/index.d.ts"
-      ],
       "vite-plugin": [
         "dist/esm/vite/index.d.ts"
       ]

package/dist/cjs/auth/useAuth.test.d.ts

@@ -1 +0,0 @@
-export {};

package/dist/cjs/auth/useAuth.test.js

@@ -1,96 +0,0 @@
-"use strict";
-Object.defineProperty(exports, "__esModule", { value: true });
-const vitest_1 = require("vitest");
-/**
- * The signed-out redirect on internal apps.
- *
- * A separate file from `index.test.ts` because it has to replace
- * `better-auth/react` wholesale to drive `useSession`, and that would strip the
- * real client the export tests next door assert against.
- *
- * The value here is entirely in WHICH signed-out renders it reacts to. An
- * external app has a real logged-out state, and an app built before the
- * platform sent an access mode tells us nothing — redirecting either turns a
- * working public page into a forced sign-in.
- */
-const { useSessionMock } = vitest_1.vi.hoisted(() => ({ useSessionMock: vitest_1.vi.fn() }));
-vitest_1.vi.mock('better-auth/react', () => ({
-    createAuthClient: () => ({
-        useSession: useSessionMock,
-        signIn: {},
-        signUp: {},
-        signOut: vitest_1.vi.fn(),
-        updateUser: vitest_1.vi.fn(),
-    }),
-}));
-vitest_1.vi.mock('better-auth/client/plugins', () => ({
-    magicLinkClient: () => ({}),
-    inferAdditionalFields: () => ({}),
-}));
-// `useAuth` takes only `useEffect` from React. Running it inline is the whole
-// of what a render would do here, and avoids pulling in a renderer.
-vitest_1.vi.mock('react', () => ({ useEffect: (fn) => fn() }));
-const index_js_1 = require("./index.js");
-const APP_URL = 'https://app.zite.so/dashboard';
-function stubLocation(href) {
-    const location = { pathname: new URL(href).pathname, href };
-    vitest_1.vi.stubGlobal('window', { location });
-    return location;
-}
-const signedOut = { data: null, isPending: false };
-(0, vitest_1.beforeEach)(() => {
-    delete process.env.ZITE_ACCESS_MODE;
-});
-(0, vitest_1.afterEach)(() => {
-    delete process.env.ZITE_ACCESS_MODE;
-    vitest_1.vi.unstubAllGlobals();
-    useSessionMock.mockReset();
-});
-const render = (session, { accessMode, href = APP_URL } = {}) => {
-    if (accessMode !== undefined)
-        process.env.ZITE_ACCESS_MODE = accessMode;
-    const location = stubLocation(href);
-    useSessionMock.mockReturnValue(session);
-    return { result: (0, index_js_1.useAuth)(), location };
-};
-(0, vitest_1.describe)('useAuth signed-out handling', () => {
-    (0, vitest_1.it)('sends a signed-out visitor on an internal app to sign-in', () => {
-        const { result, location } = render(signedOut, { accessMode: 'internal' });
-        (0, vitest_1.expect)(location.href.startsWith('/auth/login')).toBe(true);
-        // Reported as loading rather than signed out: the signed-out branch of an
-        // internal app is the empty screen this exists to prevent.
-        (0, vitest_1.expect)(result.isLoading).toBe(true);
-    });
-    (0, vitest_1.it)('leaves a signed-out visitor on an external app alone', () => {
-        const { result, location } = render(signedOut, { accessMode: 'external' });
-        (0, vitest_1.expect)(location.href).toBe(APP_URL);
-        (0, vitest_1.expect)(result.isLoading).toBe(false);
-        (0, vitest_1.expect)(result.user).toBe(null);
-    });
-    // Every app published before the platform started sending an access mode.
-    (0, vitest_1.it)('leaves an app that never declared an access mode alone', () => {
-        const { result, location } = render(signedOut);
-        (0, vitest_1.expect)(location.href).toBe(APP_URL);
-        (0, vitest_1.expect)(result.isLoading).toBe(false);
-    });
-    (0, vitest_1.it)('does not redirect while the session is still resolving', () => {
-        const { result, location } = render({ data: null, isPending: true }, { accessMode: 'internal' });
-        (0, vitest_1.expect)(location.href).toBe(APP_URL);
-        (0, vitest_1.expect)(result.isLoading).toBe(true);
-    });
-    (0, vitest_1.it)('does not redirect a signed-in visitor', () => {
-        const { result, location } = render({ data: { user: { id: 'u1', email: 'a@b.com' } }, isPending: false }, { accessMode: 'internal' });
-        (0, vitest_1.expect)(location.href).toBe(APP_URL);
-        (0, vitest_1.expect)(result.isLoading).toBe(false);
-        (0, vitest_1.expect)(result.user).toMatchObject({ id: 'u1' });
-    });
-    // `loginWithRedirect` refuses to navigate away from an auth page, so claiming
-    // a redirect here would hang the caller on `isLoading` forever.
-    (0, vitest_1.it)('does not claim to be loading on an auth page it cannot leave', () => {
-        const { result } = render(signedOut, {
-            accessMode: 'internal',
-            href: 'https://app.zite.so/auth/login',
-        });
-        (0, vitest_1.expect)(result.isLoading).toBe(false);
-    });
-});

package/dist/esm/auth/useAuth.test.d.ts

@@ -1 +0,0 @@
-export {};

package/dist/esm/auth/useAuth.test.js

@@ -1,94 +0,0 @@
-import { describe, it, expect, afterEach, beforeEach, vi } from 'vitest';
-/**
- * The signed-out redirect on internal apps.
- *
- * A separate file from `index.test.ts` because it has to replace
- * `better-auth/react` wholesale to drive `useSession`, and that would strip the
- * real client the export tests next door assert against.
- *
- * The value here is entirely in WHICH signed-out renders it reacts to. An
- * external app has a real logged-out state, and an app built before the
- * platform sent an access mode tells us nothing — redirecting either turns a
- * working public page into a forced sign-in.
- */
-const { useSessionMock } = vi.hoisted(() => ({ useSessionMock: vi.fn() }));
-vi.mock('better-auth/react', () => ({
-    createAuthClient: () => ({
-        useSession: useSessionMock,
-        signIn: {},
-        signUp: {},
-        signOut: vi.fn(),
-        updateUser: vi.fn(),
-    }),
-}));
-vi.mock('better-auth/client/plugins', () => ({
-    magicLinkClient: () => ({}),
-    inferAdditionalFields: () => ({}),
-}));
-// `useAuth` takes only `useEffect` from React. Running it inline is the whole
-// of what a render would do here, and avoids pulling in a renderer.
-vi.mock('react', () => ({ useEffect: (fn) => fn() }));
-import { useAuth } from './index.js';
-const APP_URL = 'https://app.zite.so/dashboard';
-function stubLocation(href) {
-    const location = { pathname: new URL(href).pathname, href };
-    vi.stubGlobal('window', { location });
-    return location;
-}
-const signedOut = { data: null, isPending: false };
-beforeEach(() => {
-    delete process.env.ZITE_ACCESS_MODE;
-});
-afterEach(() => {
-    delete process.env.ZITE_ACCESS_MODE;
-    vi.unstubAllGlobals();
-    useSessionMock.mockReset();
-});
-const render = (session, { accessMode, href = APP_URL } = {}) => {
-    if (accessMode !== undefined)
-        process.env.ZITE_ACCESS_MODE = accessMode;
-    const location = stubLocation(href);
-    useSessionMock.mockReturnValue(session);
-    return { result: useAuth(), location };
-};
-describe('useAuth signed-out handling', () => {
-    it('sends a signed-out visitor on an internal app to sign-in', () => {
-        const { result, location } = render(signedOut, { accessMode: 'internal' });
-        expect(location.href.startsWith('/auth/login')).toBe(true);
-        // Reported as loading rather than signed out: the signed-out branch of an
-        // internal app is the empty screen this exists to prevent.
-        expect(result.isLoading).toBe(true);
-    });
-    it('leaves a signed-out visitor on an external app alone', () => {
-        const { result, location } = render(signedOut, { accessMode: 'external' });
-        expect(location.href).toBe(APP_URL);
-        expect(result.isLoading).toBe(false);
-        expect(result.user).toBe(null);
-    });
-    // Every app published before the platform started sending an access mode.
-    it('leaves an app that never declared an access mode alone', () => {
-        const { result, location } = render(signedOut);
-        expect(location.href).toBe(APP_URL);
-        expect(result.isLoading).toBe(false);
-    });
-    it('does not redirect while the session is still resolving', () => {
-        const { result, location } = render({ data: null, isPending: true }, { accessMode: 'internal' });
-        expect(location.href).toBe(APP_URL);
-        expect(result.isLoading).toBe(true);
-    });
-    it('does not redirect a signed-in visitor', () => {
-        const { result, location } = render({ data: { user: { id: 'u1', email: 'a@b.com' } }, isPending: false }, { accessMode: 'internal' });
-        expect(location.href).toBe(APP_URL);
-        expect(result.isLoading).toBe(false);
-        expect(result.user).toMatchObject({ id: 'u1' });
-    });
-    // `loginWithRedirect` refuses to navigate away from an auth page, so claiming
-    // a redirect here would hang the caller on `isLoading` forever.
-    it('does not claim to be loading on an auth page it cannot leave', () => {
-        const { result } = render(signedOut, {
-            accessMode: 'internal',
-            href: 'https://app.zite.so/auth/login',
-        });
-        expect(result.isLoading).toBe(false);
-    });
-});