@valbuild/shared 0.143.0 → 0.144.2

package/dist/declarations/src/internal/publish/contentApi.d.ts

@@ -426,4 +426,10 @@ export type PublishTabJob = {
     base: string | null;
     /** The changes its build is to include, on top of `base`. */
     patches: string[];
+    /**
+     * Its content goes live on the build already live: content's prepare found
+     * it changes only Val content, which that build shows, so nothing is built
+     * for it. Set on the answer that hands it over (`step: null`).
+     */
+    contentOnly?: true;
 };

package/dist/declarations/src/internal/richtext/richTextImages.d.ts

@@ -0,0 +1,21 @@
+import type { SerializedImageSchema, SerializedRichTextSchema, SourcePath } from "@valbuild/core";
+/**
+ * The image schema a rich text field's inline `img` nodes are validated with,
+ * when it is a real schema rather than `img: true`.
+ *
+ * It is the only way a rich text field can point INTO a gallery
+ * (`s.richtext({ img: s.image(galleryVal) })`), which is why every reference
+ * scan has to ask: the field's own schema is `richtext`, not `image`, so a walk
+ * that only looks for image leaves walks straight past the images in it.
+ */
+export declare function richTextImageSchema(schema: SerializedRichTextSchema): SerializedImageSchema | null;
+/**
+ * Every inline image in a rich text value, at the path of its `src`.
+ *
+ * `src` is a media value (`{ path, … }`), so the path handed out is one a
+ * patch can address — `field.0."children".1."src"` — and a rename rewrites
+ * `[…, "src", "path"]` there with the same op it uses on an image field.
+ * Images nest (a list item holds a paragraph holds the image), so the walk
+ * follows `children` all the way down.
+ */
+export declare function forEachRichTextImage(path: SourcePath, source: unknown, visit: (srcPath: SourcePath, src: Record<string, unknown>) => void): void;

package/dist/declarations/src/internal/server/types.d.ts

@@ -1,7 +1,7 @@
 import { Json } from "@valbuild/core";
-export declare const VAL_SESSION_COOKIE: "val_session";
-export declare const VAL_STATE_COOKIE: "val_state";
-export declare const VAL_ENABLE_COOKIE_NAME: "val_enable";
+export declare const VAL_SESSION_COOKIE: any;
+export declare const VAL_STATE_COOKIE: any;
+export declare const VAL_ENABLE_COOKIE_NAME: any;
 export type VAL_SESSION_COOKIE = typeof VAL_SESSION_COOKIE;
 export type VAL_STATE_COOKIE = typeof VAL_STATE_COOKIE;
 export type VAL_ENABLE_COOKIE_NAME = typeof VAL_ENABLE_COOKIE_NAME;

package/dist/declarations/src/internal/validation/partitionValidationErrors.d.ts

@@ -5,7 +5,8 @@ import type { SourcePath, ValidationError } from "@valbuild/core";
  * `skipped` errors carry only fix codes the user can't (or shouldn't) act on
  * in the browser:
  *   - image/file metadata checks (need to read bytes from disk)
- *   - remote upload/download/check (need a personal access token + network)
+ *   - remote upload/download, and the singular remote check (need a personal
+ *     access token + network)
  *   - gallery directory uniqueness + untracked-files checks (need fs traversal)
  *
  * The server (ValOps + createFixPatch) resolves all of these automatically on

package/dist/declarations/src/internal/zod/History.d.ts

@@ -66,7 +66,7 @@ export type BinaryFileRef = z.infer<typeof BinaryFileRef>;
 export declare const HistoricalModule: z.ZodObject<{
     source: z.ZodNullable<z.ZodType<JSONValueT, unknown, z.core.$ZodTypeInternals<JSONValueT, unknown>>>;
     schema: z.ZodNullable<z.ZodType<SerializedSchemaT, unknown, z.core.$ZodTypeInternals<SerializedSchemaT, unknown>>>;
-    patchIds: z.ZodArray<z.ZodString & z.ZodType<import("@valbuild/core").PatchId, string, z.core.$ZodTypeInternals<import("@valbuild/core").PatchId, string>>>;
+    patchIds: z.ZodArray<z.ZodString & z.ZodType<PatchIdT, string, z.core.$ZodTypeInternals<PatchIdT, string>>>;
     changedPaths: z.ZodArray<z.ZodString>;
     failures: z.ZodArray<z.ZodDiscriminatedUnion<[z.ZodObject<{
         kind: z.ZodLiteral<"commit-not-found">;
@@ -111,7 +111,7 @@ export declare const HistoricalPatchSet: z.ZodObject<{
     modules: z.ZodRecord<z.ZodString, z.ZodObject<{
         source: z.ZodNullable<z.ZodType<JSONValueT, unknown, z.core.$ZodTypeInternals<JSONValueT, unknown>>>;
         schema: z.ZodNullable<z.ZodType<SerializedSchemaT, unknown, z.core.$ZodTypeInternals<SerializedSchemaT, unknown>>>;
-        patchIds: z.ZodArray<z.ZodString & z.ZodType<import("@valbuild/core").PatchId, string, z.core.$ZodTypeInternals<import("@valbuild/core").PatchId, string>>>;
+        patchIds: z.ZodArray<z.ZodString & z.ZodType<PatchIdT, string, z.core.$ZodTypeInternals<PatchIdT, string>>>;
         changedPaths: z.ZodArray<z.ZodString>;
         failures: z.ZodArray<z.ZodDiscriminatedUnion<[z.ZodObject<{
             kind: z.ZodLiteral<"commit-not-found">;
@@ -139,7 +139,7 @@ export declare const HistoricalPatchSet: z.ZodObject<{
         }, z.core.$strip>], "kind">>;
     }, z.core.$strip>>;
     patches: z.ZodArray<z.ZodObject<{
-        patchId: z.ZodString & z.ZodType<import("@valbuild/core").PatchId, string, z.core.$ZodTypeInternals<import("@valbuild/core").PatchId, string>>;
+        patchId: z.ZodString & z.ZodType<PatchIdT, string, z.core.$ZodTypeInternals<PatchIdT, string>>;
         moduleFilePath: z.ZodString;
         patch: z.ZodUnknown;
         authorId: z.ZodNullable<z.ZodString>;

package/dist/declarations/src/internal/zod/Patch.d.ts

@@ -1,5 +1,4 @@
 import type { JSONValue as JSONValueT, PatchJSON as PatchJSONT, PatchBlock as PatchBlockT, ParentRef as ParentRefT } from "@valbuild/core/patch";
-import type { PatchId as PatchIdT } from "@valbuild/core";
 import { z } from "zod";
 /**
  * JSON, recursively — the shape of a Source over the wire.

package/dist/declarations/src/internal/zod/SerializedSchema.d.ts

@@ -83,7 +83,7 @@ export declare const SerializedSettingsSchema: z.ZodType<SerializedSettingsSchem
  */
 export declare const SerializedValViewSchema: z.ZodObject<{
     type: z.ZodLiteral<"view">;
-    moduleFilePath: z.ZodType<import("@valbuild/core").ModuleFilePath, unknown, z.core.$ZodTypeInternals<import("@valbuild/core").ModuleFilePath, unknown>>;
+    moduleFilePath: z.ZodType<ModuleFilePathT, unknown, z.core.$ZodTypeInternals<ModuleFilePathT, unknown>>;
     opt: z.ZodLiteral<false>;
     readonly: z.ZodOptional<z.ZodBoolean>;
     hidden: z.ZodOptional<z.ZodBoolean>;

package/internal/dist/valbuild-shared-internal.cjs.dev.js

@@ -2,8 +2,8 @@
 
 Object.defineProperty(exports, '__esModule', { value: true });
 
-var core = require('@valbuild/core');
 var getSitemapTree = require('../../dist/getSitemapTree-c732e09a.cjs.dev.js');
+var core = require('@valbuild/core');
 var zod = require('zod');
 var zodValidationError = require('zod-validation-error');
 var FlexSearch = require('flexsearch');
@@ -657,6 +657,105 @@ function convertListItemToRemirrorParagraph(rtChildren) {
   return children;
 }
 
+/**
+ * The one way to build a child's source path.
+ *
+ * There were five hand-rolled versions of this, three of them subtly different
+ * and two of them wrong, and the wrong ones were wrong in a way that hid: a
+ * module path segment has to be JSON-quoted if it is a string and bare if it is
+ * an array index, and both broken copies appended the raw key at the module
+ * root. An unquoted key parses fine as long as it contains no `.` — so every
+ * object field and every ordinary record key still resolved, and only a key with
+ * a dot in it broke. That is exactly what a media gallery is keyed by, so
+ * clicking a file in the Media panel navigated to
+ * `?p=/public/val/red-8x8_bfbd0.png`, which `splitModulePath` reads as the two
+ * segments `/public/val/red-8x8_bfbd0` and `png`, and the studio said the module
+ * was not found.
+ *
+ * So: one function, and never a template string. `Internal.createValPathOfItem`
+ * is the rule itself — `JSON.stringify` quotes a string and leaves a number
+ * bare, which is precisely the module-path grammar — and everything here defers
+ * to it rather than restating it.
+ */
+function sourcePathOfChild(parent, key) {
+  /**
+   * A parent that is already `…?p=` gets the key with no separator.
+   *
+   * The search index walks from `moduleFilePath + "?p="` rather than from the
+   * module file path, so that every path it produces has a module path — and
+   * `createValPathOfItem` would see the separator and join with a `.`, giving
+   * `?p=."title"`.
+   */
+  if (parent.endsWith(core.Internal.ModuleFilePathSep)) {
+    return "".concat(parent).concat(JSON.stringify(key));
+  }
+  var path = core.Internal.createValPathOfItem(parent, key);
+  if (path === undefined) {
+    // Only when the parent is empty, which callers cannot produce: every walk
+    // starts from a module file path. Thrown rather than skipped so a future
+    // change that breaks that assumption is loud.
+    throw new Error("Could not build a source path for '".concat(key, "' under ").concat(parent));
+  }
+  return path;
+}
+
+/**
+ * The same thing, for callers holding the module file path and module path apart.
+ *
+ * `ModulePath` is empty at the module root, which is the case both broken copies
+ * got wrong: there is no separator in the path yet, so the key is the first
+ * segment and still has to be quoted.
+ */
+function concatModulePath(moduleFilePath, modulePath, key) {
+  return sourcePathOfChild(modulePath ? core.Internal.joinModuleFilePathAndModulePath(moduleFilePath, modulePath) : moduleFilePath, key);
+}
+
+/**
+ * The image schema a rich text field's inline `img` nodes are validated with,
+ * when it is a real schema rather than `img: true`.
+ *
+ * It is the only way a rich text field can point INTO a gallery
+ * (`s.richtext({ img: s.image(galleryVal) })`), which is why every reference
+ * scan has to ask: the field's own schema is `richtext`, not `image`, so a walk
+ * that only looks for image leaves walks straight past the images in it.
+ */
+function richTextImageSchema(schema) {
+  var _schema$options;
+  var img = (_schema$options = schema.options) === null || _schema$options === void 0 ? void 0 : _schema$options.img;
+  return getSitemapTree._typeof(img) === "object" && img !== null ? img : null;
+}
+
+/**
+ * Every inline image in a rich text value, at the path of its `src`.
+ *
+ * `src` is a media value (`{ path, … }`), so the path handed out is one a
+ * patch can address — `field.0."children".1."src"` — and a rename rewrites
+ * `[…, "src", "path"]` there with the same op it uses on an image field.
+ * Images nest (a list item holds a paragraph holds the image), so the walk
+ * follows `children` all the way down.
+ */
+function forEachRichTextImage(path, source, visit) {
+  if (!Array.isArray(source)) {
+    return;
+  }
+  for (var index = 0; index < source.length; index++) {
+    var node = source[index];
+    if (getSitemapTree._typeof(node) !== "object" || node === null || Array.isArray(node)) {
+      continue;
+    }
+    var nodePath = sourcePathOfChild(path, index);
+    if ("tag" in node && node.tag === "img" && "src" in node) {
+      var src = node.src;
+      if (getSitemapTree._typeof(src) === "object" && src !== null && !Array.isArray(src)) {
+        visit(sourcePathOfChild(nodePath, "src"), getSitemapTree._objectSpread2({}, src));
+      }
+    }
+    if ("children" in node) {
+      forEachRichTextImage(sourcePathOfChild(nodePath, "children"), node.children, visit);
+    }
+  }
+}
+
 var VAL_SESSION_COOKIE = core.Internal.VAL_SESSION_COOKIE;
 var VAL_STATE_COOKIE = core.Internal.VAL_STATE_COOKIE;
 var VAL_ENABLE_COOKIE_NAME = core.Internal.VAL_ENABLE_COOKIE_NAME;
@@ -1172,7 +1271,7 @@ var SerializedRecordSchema = zod.z.lazy(function () {
     dir: zod.z.string().optional(),
     remote: zod.z["boolean"]().optional(),
     encode: ImageEncodeOption.optional(),
-    // A videoset's: see `VideoStreamOption` below for why it is spelled
+    // A videodir's: see `VideoStreamOption` below for why it is spelled
     // out rather than passed through.
     stream: VideoStreamOption.optional(),
     alt: SerializedSchema.optional(),
@@ -1228,7 +1327,7 @@ var SerializedVideoSchema = zod.z.object(getSitemapTree._objectSpread2(getSitema
   options: VideoOptions.optional(),
   opt: zod.z["boolean"](),
   remote: zod.z["boolean"]().optional(),
-  // The `s.videoset()` a set-backed field picks from.
+  // The `s.videodir()` a set-backed field picks from.
   referencedModule: zod.z.string().optional()
 }));
 var DateOptions = zod.z.object({
@@ -5567,7 +5666,7 @@ function getSourceAt(source, path) {
  * Walks `schema` along `path`, returning a structured result:
  * - `leaf`: walked the full path; resolved schema at the end.
  * - `richtext`: hit a richtext mid-walk; richtext is the resolved schema.
- * - `gallery-traversed`: hit an `s.imageset()` record and walked past it (i.e. the
+ * - `gallery-traversed`: hit an `s.imagedir()` record and walked past it (i.e. the
  *   path tries to address an entry inside the gallery — a clue the AI should
  *   have used the gallery tool instead).
  * - `unresolved`: the path could not be walked.
@@ -5675,7 +5774,7 @@ function checkGallerySchema(moduleSchema) {
     // looks like a gallery from here, and the tool can do nothing with one.
     return {
       kind: "error",
-      message: "Module is a video set (s.videoset()), not an images gallery. Videos cannot be added or removed by this tool: upload them in Val Studio."
+      message: "Module is a video set (s.videodir()), not an images gallery. Videos cannot be added or removed by this tool: upload them in Val Studio."
     };
   }
   if (moduleSchema.type === "image") {
@@ -5706,7 +5805,7 @@ function buildImageGalleryPatch(args, moduleSchema) {
     op: "add",
     path: [args.filePath],
     value: getSitemapTree._objectSpread2(getSitemapTree._objectSpread2({}, args.metadata), {}, {
-      // `alt` is a REQUIRED field of a gallery entry (`s.imageset()` gives it a
+      // `alt` is a REQUIRED field of a gallery entry (`s.imagedir()` gives it a
       // nullable string schema), so an entry written without one is invalid
       // the moment it lands — and the caller that had no alt to give is the
       // common case, not the odd one. Null is what the Studio's own upload
@@ -5769,7 +5868,7 @@ function buildRemoveImageGalleryEntryPatch(args, moduleSchema, moduleSource) {
 var GALLERY_REDIRECT = {
   kind: "wrong-tool",
   suggestedTool: "add_session_image_to_gallery",
-  reason: "Destination is a media gallery (s.imageset() / s.fileset()). Gallery entries are keyed by file path and carry a file on disk, so they cannot be created with a plain patch. Use add_session_image_to_gallery."
+  reason: "Destination is a media gallery (s.imagedir() / s.filedir()). Gallery entries are keyed by file path and carry a file on disk, so they cannot be created with a plain patch. Use add_session_image_to_gallery."
 };
 
 /**
@@ -5779,10 +5878,10 @@ var GALLERY_REDIRECT = {
  */
 var VIDEOSET_REFUSAL = {
   kind: "error",
-  message: "Destination is a video set (s.videoset()). Its entries are keyed by file path and carry video files, so they cannot be created with a plain patch, and no tool here uploads a video: add it in Val Studio."
+  message: "Destination is a video set (s.videodir()). Its entries are keyed by file path and carry video files, so they cannot be created with a plain patch, and no tool here uploads a video: add it in Val Studio."
 };
 
-/** An `s.imageset()` / `s.fileset()` / `s.videoset()` record: a gallery, not an ordinary record. */
+/** An `s.imagedir()` / `s.filedir()` / `s.videodir()` record: a gallery, not an ordinary record. */
 function isGallery(schema) {
   return schema.type === "record" && schema.mediaType !== undefined;
 }
@@ -6097,7 +6196,8 @@ function describeContainerAtPath(moduleSchema, moduleSource, path) {
  * `skipped` errors carry only fix codes the user can't (or shouldn't) act on
  * in the browser:
  *   - image/file metadata checks (need to read bytes from disk)
- *   - remote upload/download/check (need a personal access token + network)
+ *   - remote upload/download, and the singular remote check (need a personal
+ *     access token + network)
  *   - gallery directory uniqueness + untracked-files checks (need fs traversal)
  *
  * The server (ValOps + createFixPatch) resolves all of these automatically on
@@ -6157,20 +6257,17 @@ function isSkippableFixCode(fix) {
     case "image:upload-remote":
     case "image:download-remote":
     case "image:check-remote":
-    case "images:check-remote":
     case "images:upload-remote":
     case "file:add-metadata":
     case "file:check-metadata":
     case "file:upload-remote":
     case "file:download-remote":
     case "file:check-remote":
-    case "files:check-remote":
     case "files:upload-remote":
     case "video:add-metadata": // the Studio writes it on upload; --fix for the rest
     case "video:upload-remote":
     case "video:download-remote":
     case "videos:add-metadata": // as `video:add-metadata`, for a set's entry
-    case "videos:check-remote":
     case "videos:upload-remote":
     case "videos:check-unique-folder":
     case "videos:check-all-files":
@@ -6181,6 +6278,18 @@ function isSkippableFixCode(fix) {
     case "view:check-module":
       // schema is code: nothing for an editor to do
       return true;
+    case "images:check-remote":
+    case "files:check-remote":
+    case "videos:check-remote":
+      // A collection KEY that is wrong as a key: a remote URL in a gallery that
+      // is not `.remote()`, one that does not parse, one outside the gallery's
+      // directory. Unlike the singular `image:check-remote` above (core's "not
+      // checked" marker on EVERY remote value, which the server does check),
+      // core emits these only when the key is wrong, and nothing repairs that
+      // on save -- not the server, not `val validate --fix`. Only a person knows
+      // whether the key or the gallery's options are the mistake. Skipping them
+      // also took them off the publish gate, so a broken key published unseen.
+      return false;
     case "keyof:check-keys":
     case "router:check-route":
     case "locale:check-locale":
@@ -6374,59 +6483,6 @@ function withExtension(filename, ext) {
   return "".concat(base, ".").concat(ext);
 }
 
-/**
- * The one way to build a child's source path.
- *
- * There were five hand-rolled versions of this, three of them subtly different
- * and two of them wrong, and the wrong ones were wrong in a way that hid: a
- * module path segment has to be JSON-quoted if it is a string and bare if it is
- * an array index, and both broken copies appended the raw key at the module
- * root. An unquoted key parses fine as long as it contains no `.` — so every
- * object field and every ordinary record key still resolved, and only a key with
- * a dot in it broke. That is exactly what a media gallery is keyed by, so
- * clicking a file in the Media panel navigated to
- * `?p=/public/val/red-8x8_bfbd0.png`, which `splitModulePath` reads as the two
- * segments `/public/val/red-8x8_bfbd0` and `png`, and the studio said the module
- * was not found.
- *
- * So: one function, and never a template string. `Internal.createValPathOfItem`
- * is the rule itself — `JSON.stringify` quotes a string and leaves a number
- * bare, which is precisely the module-path grammar — and everything here defers
- * to it rather than restating it.
- */
-function sourcePathOfChild(parent, key) {
-  /**
-   * A parent that is already `…?p=` gets the key with no separator.
-   *
-   * The search index walks from `moduleFilePath + "?p="` rather than from the
-   * module file path, so that every path it produces has a module path — and
-   * `createValPathOfItem` would see the separator and join with a `.`, giving
-   * `?p=."title"`.
-   */
-  if (parent.endsWith(core.Internal.ModuleFilePathSep)) {
-    return "".concat(parent).concat(JSON.stringify(key));
-  }
-  var path = core.Internal.createValPathOfItem(parent, key);
-  if (path === undefined) {
-    // Only when the parent is empty, which callers cannot produce: every walk
-    // starts from a module file path. Thrown rather than skipped so a future
-    // change that breaks that assumption is loud.
-    throw new Error("Could not build a source path for '".concat(key, "' under ").concat(parent));
-  }
-  return path;
-}
-
-/**
- * The same thing, for callers holding the module file path and module path apart.
- *
- * `ModulePath` is empty at the module root, which is the case both broken copies
- * got wrong: there is no separator in the path yet, so the key is the first
- * segment and still has to be quoted.
- */
-function concatModulePath(moduleFilePath, modulePath, key) {
-  return sourcePathOfChild(modulePath ? core.Internal.joinModuleFilePathAndModulePath(moduleFilePath, modulePath) : moduleFilePath, key);
-}
-
 /**
  * Traverses a schema and source pair, calling a callback for each leaf node.
  * Handles all schema types including primitives, objects, arrays, records, unions, richtext, files, images, etc.
@@ -7865,7 +7921,8 @@ var tabJob = zod.z.object({
   id: zod.z.string(),
   step: zod.z["enum"](["prepare", "build", "upload"]).nullable(),
   base: zod.z.string().nullable(),
-  patches: zod.z.array(zod.z.string())
+  patches: zod.z.array(zod.z.string()),
+  contentOnly: zod.z.literal(true).optional()
 });
 var pressResponse = zod.z.object({
   request: requestStatus,
@@ -8056,6 +8113,7 @@ exports.filterRoutesByPatterns = filterRoutesByPatterns;
 exports.findSimilar = findSimilar;
 exports.fitWithin = fitWithin;
 exports.flattenRichText = flattenRichText;
+exports.forEachRichTextImage = forEachRichTextImage;
 exports.getErrorMessageFromUnknownJson = getErrorMessageFromUnknownJson;
 exports.getFilenameFromRef = getFilenameFromRef;
 exports.getInlineImgInfo = getInlineImgInfo;
@@ -8101,6 +8159,7 @@ exports.resolvePairGround = resolvePairGround;
 exports.resolveSchemaSourceFixForError = resolveSchemaSourceFixForError;
 exports.resolveSchemaSourceFixes = resolveSchemaSourceFixes;
 exports.resolveSerializedSchemaAtPath = resolveSerializedSchemaAtPath;
+exports.richTextImageSchema = richTextImageSchema;
 exports.richTextToRemirror = richTextToRemirror;
 exports.safeParsePatch = safeParsePatch;
 exports.sourcePathOfChild = sourcePathOfChild;