zitejs 0.9.99 → 0.9.101

package/dist/cjs/bundle/index.js

@@ -213,11 +213,12 @@ function getSdkImportSource(baseDir) {
 /**
  * `zitejs/db`, `zitejs/api`, `zitejs/integrations` and `zitejs/email` are
  * tsconfig aliases onto generated files, not real package subpaths — they are
- * absent from the `exports` map, and `zitejs` isn't in PREBUNDLED_LIBS either.
- * So marking one external doesn't defer resolution, it guarantees a module
- * that fails to instantiate the first time the deployed endpoint is invoked,
- * long after the build reported success. Fail here instead, where the message
- * can name the file that's missing.
+ * absent from the `exports` map. `zitejs/backend` IS a real subpath export, but
+ * it lands here too and `zitejs` is not in PREBUNDLED_LIBS, so nothing would
+ * resolve it in the worker either. Either way, marking one external doesn't
+ * defer resolution: it guarantees a module that fails to instantiate the first
+ * time the deployed endpoint is invoked, long after the build reported success.
+ * Fail here instead, where the message can name the file that's missing.
  */
 const unresolvedAlias = (specifier, expectedPath) => {
     throw new Error(`Cannot resolve '${specifier}': expected generated file at ${expectedPath}. ` +

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

@@ -90,10 +90,18 @@ export interface TableFindAllOptions<T = Record<string, unknown>> {
      */
     sort?: unknown[];
     filters?: RecordFilters<T>;
+    /**
+     * The nested filter format (`filters` is the legacy flat one). IGNORED here
+     * for the same reason as `sort` — not in `DatabasesFindAllParamsSchema`, so
+     * zod strips it — but kept so code already passing it still compiles. It IS
+     * honored by `zite.auth.findAllUsers`.
+     */
+    filter?: unknown;
     fields?: Array<FieldSelector<T>>;
 }
 export interface BulkCreateResult<T> {
-    success: boolean;
+    /** Absent when `records: []` was passed — the dispatch short-circuits before setting it. */
+    success?: boolean;
     records: T[];
 }
 export interface UpdateResult<T> {
@@ -173,7 +181,16 @@ export type FindAllAuthUsersResult<T extends AuthUser = AuthUser> = {
     total: number;
     hasMore: boolean;
 };
-export type UpdateAuthUserProfile = Partial<Omit<AuthUser, "id" | "email" | "name">>;
+/**
+ * `null` clears a value — `publicUpdateAuthUserInputSchema` accepts
+ * `string | null | undefined` on each of these, and null is the only way to
+ * unset a name.
+ */
+export type UpdateAuthUserProfile = {
+    firstName?: string | null;
+    lastName?: string | null;
+    image?: string | null;
+};
 export interface AuthClient<T extends AuthUser = AuthUser> {
     findAllUsers(options?: FindAllAuthUsersOptions): Promise<FindAllAuthUsersResult<T>>;
     updateUserProfile(userId: string, profile: UpdateAuthUserProfile): Promise<T>;

package/dist/cjs/sync/lib.js

@@ -10,33 +10,47 @@ exports.generateBackendWrapperTs = generateBackendWrapperTs;
 exports.generateEmailSdk = generateEmailSdk;
 const parser_1 = require("@babel/parser");
 const AUTH_USERS_TABLE_ID = "zite_user";
-/** What a field's value looks like when a record is READ back. */
+/**
+ * What a field's value looks like when a record is READ back.
+ *
+ * `| null` on the nullable ones is load-bearing, not pedantry: every field
+ * column is created nullable with no default (`recordsTableManager`), and only
+ * the six text types get their NULL rewritten to `''` on the way out
+ * (`normalizeEmptyStringFields` keys on `emptyValue === ''`). The product's own
+ * test asserts `fld_number` and `fld_checkbox` read back as `null`. Typing them
+ * non-null let `task.estimate.toFixed(2)` compile and throw.
+ */
 const FIELD_TYPE_MAP = {
+    // Text: NULL is rewritten to '' on read, so these genuinely can't be null.
     single_line_text: "string",
     long_text: "string",
     rich_text: "string",
     email: "string",
     url: "string",
     phone_number: "string",
-    number: "number",
-    currency: "number",
-    percent: "number",
-    rating: "number",
-    duration: "number",
-    single_select: "string",
-    multiple_select: "string[]",
-    checkbox: "boolean",
+    number: "number | null",
+    currency: "number | null",
+    percent: "number | null",
+    rating: "number | null",
+    // DECIMAL seconds, unlike Airtable's, which is formatted to "HH:mm:ss".
+    duration: "number | null",
+    checkbox: "boolean | null",
+    single_select: "string | null",
+    multiple_select: "string[] | null",
     date: "string | null",
     datetime: "string | null",
-    attachments: "ZiteAttachment[]",
-    // base-runner normalizes both of these to an array on write and stores them
-    // that way, so a read never produces a bare string.
-    linked_record: "string[]",
-    user: "string[]",
+    attachments: "ZiteAttachment[] | null",
+    // `string | string[]`, matching the pre-monorepo type. base-runner does force
+    // an array on read today, but 1.0 code is written with `typeof x === 'string'`
+    // guards — narrowing to `string[]` turns those branches into `never` and
+    // fails the app's typecheck for no gain.
+    linked_record: "string | string[]",
+    user: "string | string[]",
     lookup: "unknown",
     rollup: "unknown",
     autonumber: "number",
-    source: "string",
+    // JSONB change metadata (`{ type: "PublicAPI", apiKeyId: 3 }`), not a string.
+    source: "unknown",
     formula: "unknown",
     created_at: "string",
     updated_at: "string",
@@ -47,9 +61,18 @@ const FIELD_TYPE_MAP = {
  * looser input than it stores.
  */
 const FIELD_INPUT_TYPE_MAP = {
-    attachments: "ZiteAttachmentInput[]",
-    linked_record: "string | string[] | null",
-    user: "string | string[] | null",
+    attachments: "ZiteAttachmentInput[] | ZiteAttachmentInput",
+    linked_record: "string | string[]",
+    user: "string | string[]",
+    multiple_select: "string | string[]",
+    date: "string | Date",
+    datetime: "string | Date",
+    number: "string | number",
+    currency: "string | number",
+    percent: "string | number",
+    rating: "string | number",
+    duration: "string | number",
+    checkbox: "string | boolean",
 };
 /**
  * Computed and system-managed fields, omitted from the generated input type
@@ -156,6 +179,13 @@ function keepValidSdkName(sdkName) {
         return undefined;
     return /^[a-zA-Z_$][a-zA-Z0-9_$]*$/.test(sdkName) ? sdkName : undefined;
 }
+/**
+ * `null` is how you CLEAR a cell — every scalar write schema in
+ * `flexible-inputs.ts` ends in `.nullable()` and update runs with
+ * `allowExplicitNull`. A write type without it makes the documented way to
+ * empty a field a compile error.
+ */
+const withNull = (type) => type.includes("null") ? type : `${type} | null`;
 function tsTypeForSchemaField(def, variant = "read") {
     if (def.type === "single_select" || def.type === "multiple_select") {
         const options = def.template
@@ -166,13 +196,19 @@ function tsTypeForSchemaField(def, variant = "read") {
                 .map((o) => `"${o.label.replace(/"/g, '\\"')}"`)
                 .join(" | ");
             const union = `${literals} | string`;
-            if (def.type === "multiple_select")
-                return `(${union})[]`;
-            return union;
+            const read = def.type === "multiple_select" ? `(${union})[] | null` : `${union} | null`;
+            if (variant === "write") {
+                return def.type === "multiple_select"
+                    ? `${union} | (${union})[] | null`
+                    : `${union} | null`;
+            }
+            return read;
         }
     }
-    if (variant === "write" && FIELD_INPUT_TYPE_MAP[def.type]) {
-        return FIELD_INPUT_TYPE_MAP[def.type];
+    if (variant === "write") {
+        const write = FIELD_INPUT_TYPE_MAP[def.type] ?? FIELD_TYPE_MAP[def.type];
+        if (write)
+            return withNull(write);
     }
     if (FIELD_TYPE_MAP[def.type])
         return FIELD_TYPE_MAP[def.type];
@@ -474,7 +510,11 @@ function generateDbTs(schema) {
             if (jsdoc) {
                 lines.push(`  /** ${jsdoc} */`);
             }
-            lines.push(`  ${field.sdkName}: ${tsType};`);
+            // Optional, matching the pre-monorepo type (`required: ['id']` — "none of
+            // these are required to be defined aside from 'id'"). A `fields:`
+            // projection omits every key it wasn't asked for, so any field really can
+            // be absent on a read.
+            lines.push(`  ${field.sdkName}?: ${tsType};`);
         }
         lines.push("};");
         lines.push("");
@@ -712,14 +752,18 @@ const AIRTABLE_FIELD_TYPE_MAP = {
     currency: "number",
     percent: "number",
     rating: "number",
-    duration: "number",
+    // Formatted to "HH:mm:ss" before it reaches the app — `formatAirtableDuration`
+    // in BOTH dispatches. Unlike the Zite DB's, which is DECIMAL seconds.
+    duration: "string",
     checkbox: "boolean",
     date: "string",
     dateTime: "string",
     singleSelect: "string",
     multipleSelects: "string[]",
     multipleAttachments: "AirtableAttachment[]",
-    multipleRecordLinks: "string[]",
+    // `string | string[]`, matching the pre-monorepo type — see the note on the
+    // Zite DB's `linked_record`.
+    multipleRecordLinks: "string | string[]",
     singleCollaborator: "{ id: string; email: string; name?: string }",
     multipleCollaborators: "Array<{ id: string; email: string; name?: string }>",
     // Read-only fields
@@ -732,7 +776,8 @@ const AIRTABLE_FIELD_TYPE_MAP = {
     lastModifiedTime: "string",
     createdBy: "{ id: string; email: string; name?: string }",
     lastModifiedBy: "{ id: string; email: string; name?: string }",
-    button: "unknown",
+    // Both dispatches extract the URL string off the button object.
+    button: "string",
     externalSyncSource: "unknown",
     aiText: "string",
 };
@@ -1013,8 +1058,22 @@ function generateBackendWrapperTs(envVarNames = []) {
         // Narrows `user` to this app's generated User. ZiteScheduledContext is
         // re-exported unchanged — a scheduled fire has no user at all, so there is
         // nothing to narrow.
+        "/**",
+        " * The user an endpoint sees. NOT the full `User` from zitejs/auth — that is",
+        " * the browser's better-auth session, and the runtime never sends its",
+        " * `name`, `emailVerified`, `image`, `createdAt` or `updatedAt` to an",
+        " * endpoint. Typing those here let `context.user.createdAt.getFullYear()`",
+        " * compile and throw. `Omit` keeps any index signature merged in by",
+        " * `.zite/user-extensions.d.ts`, so a migrated user-sync app still reads its",
+        " * synced columns off this.",
+        " */",
+        "export type ZiteEndpointUser = Omit<",
+        "  User,",
+        "  'name' | 'emailVerified' | 'image' | 'createdAt' | 'updatedAt'",
+        ">;",
+        "",
         'export interface ZiteRequestContext extends Omit<_ZiteRequestContext, "user"> {',
-        "  user: User;",
+        "  user: ZiteEndpointUser;",
         "}",
         "",
         "type SchemaLike<TOut, TIn = TOut> = { _output: TOut; _input: TIn; parse: (data: unknown) => TOut };",

package/dist/esm/bundle/index.js

@@ -177,11 +177,12 @@ function getSdkImportSource(baseDir) {
 /**
  * `zitejs/db`, `zitejs/api`, `zitejs/integrations` and `zitejs/email` are
  * tsconfig aliases onto generated files, not real package subpaths — they are
- * absent from the `exports` map, and `zitejs` isn't in PREBUNDLED_LIBS either.
- * So marking one external doesn't defer resolution, it guarantees a module
- * that fails to instantiate the first time the deployed endpoint is invoked,
- * long after the build reported success. Fail here instead, where the message
- * can name the file that's missing.
+ * absent from the `exports` map. `zitejs/backend` IS a real subpath export, but
+ * it lands here too and `zitejs` is not in PREBUNDLED_LIBS, so nothing would
+ * resolve it in the worker either. Either way, marking one external doesn't
+ * defer resolution: it guarantees a module that fails to instantiate the first
+ * time the deployed endpoint is invoked, long after the build reported success.
+ * Fail here instead, where the message can name the file that's missing.
  */
 const unresolvedAlias = (specifier, expectedPath) => {
     throw new Error(`Cannot resolve '${specifier}': expected generated file at ${expectedPath}. ` +

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

@@ -90,10 +90,18 @@ export interface TableFindAllOptions<T = Record<string, unknown>> {
      */
     sort?: unknown[];
     filters?: RecordFilters<T>;
+    /**
+     * The nested filter format (`filters` is the legacy flat one). IGNORED here
+     * for the same reason as `sort` — not in `DatabasesFindAllParamsSchema`, so
+     * zod strips it — but kept so code already passing it still compiles. It IS
+     * honored by `zite.auth.findAllUsers`.
+     */
+    filter?: unknown;
     fields?: Array<FieldSelector<T>>;
 }
 export interface BulkCreateResult<T> {
-    success: boolean;
+    /** Absent when `records: []` was passed — the dispatch short-circuits before setting it. */
+    success?: boolean;
     records: T[];
 }
 export interface UpdateResult<T> {
@@ -173,7 +181,16 @@ export type FindAllAuthUsersResult<T extends AuthUser = AuthUser> = {
     total: number;
     hasMore: boolean;
 };
-export type UpdateAuthUserProfile = Partial<Omit<AuthUser, "id" | "email" | "name">>;
+/**
+ * `null` clears a value — `publicUpdateAuthUserInputSchema` accepts
+ * `string | null | undefined` on each of these, and null is the only way to
+ * unset a name.
+ */
+export type UpdateAuthUserProfile = {
+    firstName?: string | null;
+    lastName?: string | null;
+    image?: string | null;
+};
 export interface AuthClient<T extends AuthUser = AuthUser> {
     findAllUsers(options?: FindAllAuthUsersOptions): Promise<FindAllAuthUsersResult<T>>;
     updateUserProfile(userId: string, profile: UpdateAuthUserProfile): Promise<T>;

package/dist/esm/sync/lib.js

@@ -1,32 +1,46 @@
 import { parse } from "@babel/parser";
 const AUTH_USERS_TABLE_ID = "zite_user";
-/** What a field's value looks like when a record is READ back. */
+/**
+ * What a field's value looks like when a record is READ back.
+ *
+ * `| null` on the nullable ones is load-bearing, not pedantry: every field
+ * column is created nullable with no default (`recordsTableManager`), and only
+ * the six text types get their NULL rewritten to `''` on the way out
+ * (`normalizeEmptyStringFields` keys on `emptyValue === ''`). The product's own
+ * test asserts `fld_number` and `fld_checkbox` read back as `null`. Typing them
+ * non-null let `task.estimate.toFixed(2)` compile and throw.
+ */
 const FIELD_TYPE_MAP = {
+    // Text: NULL is rewritten to '' on read, so these genuinely can't be null.
     single_line_text: "string",
     long_text: "string",
     rich_text: "string",
     email: "string",
     url: "string",
     phone_number: "string",
-    number: "number",
-    currency: "number",
-    percent: "number",
-    rating: "number",
-    duration: "number",
-    single_select: "string",
-    multiple_select: "string[]",
-    checkbox: "boolean",
+    number: "number | null",
+    currency: "number | null",
+    percent: "number | null",
+    rating: "number | null",
+    // DECIMAL seconds, unlike Airtable's, which is formatted to "HH:mm:ss".
+    duration: "number | null",
+    checkbox: "boolean | null",
+    single_select: "string | null",
+    multiple_select: "string[] | null",
     date: "string | null",
     datetime: "string | null",
-    attachments: "ZiteAttachment[]",
-    // base-runner normalizes both of these to an array on write and stores them
-    // that way, so a read never produces a bare string.
-    linked_record: "string[]",
-    user: "string[]",
+    attachments: "ZiteAttachment[] | null",
+    // `string | string[]`, matching the pre-monorepo type. base-runner does force
+    // an array on read today, but 1.0 code is written with `typeof x === 'string'`
+    // guards — narrowing to `string[]` turns those branches into `never` and
+    // fails the app's typecheck for no gain.
+    linked_record: "string | string[]",
+    user: "string | string[]",
     lookup: "unknown",
     rollup: "unknown",
     autonumber: "number",
-    source: "string",
+    // JSONB change metadata (`{ type: "PublicAPI", apiKeyId: 3 }`), not a string.
+    source: "unknown",
     formula: "unknown",
     created_at: "string",
     updated_at: "string",
@@ -37,9 +51,18 @@ const FIELD_TYPE_MAP = {
  * looser input than it stores.
  */
 const FIELD_INPUT_TYPE_MAP = {
-    attachments: "ZiteAttachmentInput[]",
-    linked_record: "string | string[] | null",
-    user: "string | string[] | null",
+    attachments: "ZiteAttachmentInput[] | ZiteAttachmentInput",
+    linked_record: "string | string[]",
+    user: "string | string[]",
+    multiple_select: "string | string[]",
+    date: "string | Date",
+    datetime: "string | Date",
+    number: "string | number",
+    currency: "string | number",
+    percent: "string | number",
+    rating: "string | number",
+    duration: "string | number",
+    checkbox: "string | boolean",
 };
 /**
  * Computed and system-managed fields, omitted from the generated input type
@@ -146,6 +169,13 @@ function keepValidSdkName(sdkName) {
         return undefined;
     return /^[a-zA-Z_$][a-zA-Z0-9_$]*$/.test(sdkName) ? sdkName : undefined;
 }
+/**
+ * `null` is how you CLEAR a cell — every scalar write schema in
+ * `flexible-inputs.ts` ends in `.nullable()` and update runs with
+ * `allowExplicitNull`. A write type without it makes the documented way to
+ * empty a field a compile error.
+ */
+const withNull = (type) => type.includes("null") ? type : `${type} | null`;
 function tsTypeForSchemaField(def, variant = "read") {
     if (def.type === "single_select" || def.type === "multiple_select") {
         const options = def.template
@@ -156,13 +186,19 @@ function tsTypeForSchemaField(def, variant = "read") {
                 .map((o) => `"${o.label.replace(/"/g, '\\"')}"`)
                 .join(" | ");
             const union = `${literals} | string`;
-            if (def.type === "multiple_select")
-                return `(${union})[]`;
-            return union;
+            const read = def.type === "multiple_select" ? `(${union})[] | null` : `${union} | null`;
+            if (variant === "write") {
+                return def.type === "multiple_select"
+                    ? `${union} | (${union})[] | null`
+                    : `${union} | null`;
+            }
+            return read;
         }
     }
-    if (variant === "write" && FIELD_INPUT_TYPE_MAP[def.type]) {
-        return FIELD_INPUT_TYPE_MAP[def.type];
+    if (variant === "write") {
+        const write = FIELD_INPUT_TYPE_MAP[def.type] ?? FIELD_TYPE_MAP[def.type];
+        if (write)
+            return withNull(write);
     }
     if (FIELD_TYPE_MAP[def.type])
         return FIELD_TYPE_MAP[def.type];
@@ -464,7 +500,11 @@ export function generateDbTs(schema) {
             if (jsdoc) {
                 lines.push(`  /** ${jsdoc} */`);
             }
-            lines.push(`  ${field.sdkName}: ${tsType};`);
+            // Optional, matching the pre-monorepo type (`required: ['id']` — "none of
+            // these are required to be defined aside from 'id'"). A `fields:`
+            // projection omits every key it wasn't asked for, so any field really can
+            // be absent on a read.
+            lines.push(`  ${field.sdkName}?: ${tsType};`);
         }
         lines.push("};");
         lines.push("");
@@ -702,14 +742,18 @@ const AIRTABLE_FIELD_TYPE_MAP = {
     currency: "number",
     percent: "number",
     rating: "number",
-    duration: "number",
+    // Formatted to "HH:mm:ss" before it reaches the app — `formatAirtableDuration`
+    // in BOTH dispatches. Unlike the Zite DB's, which is DECIMAL seconds.
+    duration: "string",
     checkbox: "boolean",
     date: "string",
     dateTime: "string",
     singleSelect: "string",
     multipleSelects: "string[]",
     multipleAttachments: "AirtableAttachment[]",
-    multipleRecordLinks: "string[]",
+    // `string | string[]`, matching the pre-monorepo type — see the note on the
+    // Zite DB's `linked_record`.
+    multipleRecordLinks: "string | string[]",
     singleCollaborator: "{ id: string; email: string; name?: string }",
     multipleCollaborators: "Array<{ id: string; email: string; name?: string }>",
     // Read-only fields
@@ -722,7 +766,8 @@ const AIRTABLE_FIELD_TYPE_MAP = {
     lastModifiedTime: "string",
     createdBy: "{ id: string; email: string; name?: string }",
     lastModifiedBy: "{ id: string; email: string; name?: string }",
-    button: "unknown",
+    // Both dispatches extract the URL string off the button object.
+    button: "string",
     externalSyncSource: "unknown",
     aiText: "string",
 };
@@ -1003,8 +1048,22 @@ export function generateBackendWrapperTs(envVarNames = []) {
         // Narrows `user` to this app's generated User. ZiteScheduledContext is
         // re-exported unchanged — a scheduled fire has no user at all, so there is
         // nothing to narrow.
+        "/**",
+        " * The user an endpoint sees. NOT the full `User` from zitejs/auth — that is",
+        " * the browser's better-auth session, and the runtime never sends its",
+        " * `name`, `emailVerified`, `image`, `createdAt` or `updatedAt` to an",
+        " * endpoint. Typing those here let `context.user.createdAt.getFullYear()`",
+        " * compile and throw. `Omit` keeps any index signature merged in by",
+        " * `.zite/user-extensions.d.ts`, so a migrated user-sync app still reads its",
+        " * synced columns off this.",
+        " */",
+        "export type ZiteEndpointUser = Omit<",
+        "  User,",
+        "  'name' | 'emailVerified' | 'image' | 'createdAt' | 'updatedAt'",
+        ">;",
+        "",
         'export interface ZiteRequestContext extends Omit<_ZiteRequestContext, "user"> {',
-        "  user: User;",
+        "  user: ZiteEndpointUser;",
         "}",
         "",
         "type SchemaLike<TOut, TIn = TOut> = { _output: TOut; _input: TIn; parse: (data: unknown) => TOut };",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "zitejs",
-  "version": "0.9.99",
+  "version": "0.9.101",
   "description": "The Zite framework — build apps on Zite Database",
   "type": "module",
   "main": "./dist/cjs/index.js",