@pretextbook/pretext-html 0.16.1 → 0.18.0

package/dist/cli.d.ts

@@ -1,4 +1,4 @@
-import { RenderOptions } from './renderer.js';
+import { RenderOptions, RenderResult } from './renderer.js';
 interface CliArgs {
     options: RenderOptions;
     output?: string;
@@ -13,5 +13,16 @@ interface CliArgs {
     printPreview?: string | true;
 }
 export declare function parseArgs(argv: string[]): CliArgs;
+/**
+ * Point the page's `external/` and `generated/` URLs at the project's files,
+ * relative to `pageDir`, so a page written to disk opens with its images.
+ *
+ * A real build copies both directories next to its pages; the CLI writes one
+ * page and copies nothing, so it links the files where they are. A file that
+ * does not exist gets the same placeholder the VS Code preview shows, which
+ * says what to generate. A file on another drive than the page (Windows) has
+ * no relative path, and gets an absolute file URL instead.
+ */
+export declare function linkAssetsFrom(html: string, assetDirs: RenderResult["assetDirs"], pageDir: string): string;
 export declare function main(argv: string[]): Promise<void>;
 export {};

package/dist/cli.js

@@ -1,8 +1,13 @@
+import "node:fs";
 import "node:fs/promises";
+import "node:path";
 import "node:process";
+import "node:url";
+import "./assets.js";
 import "./printout.js";
-import { m as i, l as s } from "./cli-DzlCZymu.js";
+import { u as n, q as A, v as f } from "./cli-CKAOX3L6.js";
 export {
-  i as main,
-  s as parseArgs
+  n as linkAssetsFrom,
+  A as main,
+  f as parseArgs
 };

package/dist/index.browser.d.ts

@@ -12,8 +12,9 @@
  *    false; several engines still do not ship it.
  *  - **Pass `sourceContent`.** There is no filesystem, so `sourcePath` serves
  *    only as a virtual base for URL and xi:include resolution.
- *  - **`xi:include`s are not resolved from disk.** Pre-merge them, or pass the
- *    already-merged document as `sourceContent`.
+ *  - **`xi:include`s are not resolved from disk.** Supply the project's files
+ *    through `readSource` or `files` and they are resolved from there — or
+ *    pre-merge them and pass the merged document as `sourceContent`.
  *  - **Use `contextSourceContent`, not `contextSourcePath`**, to place a
  *    fragment in its document for correct numbering and resolved `<xref>`s
  *    (see `RenderOptions.contextSourceContent`) — `contextSourcePath` alone
@@ -21,11 +22,15 @@
  *  - **Assets come from jsDelivr by default**, version-pinned to this package.
  *    Call `setAssetsBase()` before the first render to self-host.
  */
-export { renderHtml, defaultXslDir, isJspiAvailable, xpathStringLiteral, } from './renderer.js';
-export type { RenderOptions, RenderResult } from './renderer.js';
+export { renderHtml, measureDocument, defaultSourceCache, defaultXslDir, isJspiAvailable, xpathStringLiteral, } from './renderer.js';
+export type { DocumentSize, RenderOptions, RenderResult, SourceOptions, } from './renderer.js';
+export type { SubtreeOptions } from './subtree.js';
+export { SourceCache } from './source-cache.js';
+export type { SourceCacheOptions } from './source-cache.js';
+export type { SourceReader } from './xinclude.js';
 export { findSourceMapEntry } from './sourcemap.js';
 export type { PtxSourceMap, SourceMapEntry } from './sourcemap.js';
-export { forcePortablePublication } from './publication.js';
+export { forcePreviewPublication, forcePortablePublication, } from './publication.js';
 export type { PublicationOverrides } from './publication.js';
 export { detectRenderTarget } from './target.js';
 export type { RenderTarget } from './target.js';