@vectojs/markdown 0.22.0 → 0.23.0

package/dist/markdown-abbr.d.ts

@@ -54,14 +54,6 @@ export interface AbbrDefToken {
  * paragraph rather than recognised.
  */
 export declare const ABBR_EXTENSIONS: TokenizerAndRendererExtension[];
-/**
- * Whether `text` contains an abbreviation-definition line at all.
- *
- * Cheap reject first (`*[` is rare outside this construct), matching every
- * other opener-detector in this package (`hasContainerOpener`,
- * `hasFootnoteDefOpener`).
- */
-export declare function hasAbbrDef(text: string): boolean;
 /**
  * Scan top-level tokens for `abbrDef` entries and build the term dictionary.
  *

package/dist/markdown-image.d.ts

@@ -36,19 +36,6 @@ export declare function paragraphHasImage(token: Tokens.Paragraph): boolean;
  * tier check and the flattening the render arms do cannot drift apart.
  */
 export declare function containsImage(tokens: Token[] | undefined): boolean;
-/**
- * An inline run with nested images lifted to the top level, in source order.
- *
- * The paragraph arm splits a run into one `Stack` child per image plus one per
- * maximal run of non-image tokens, which requires every image to be a direct
- * member of the array it iterates. An image inside a link or an emphasis is not,
- * so the run is flattened first.
- *
- * A wrapper is replaced by its children rather than dropped, so the text inside a
- * link that also holds an image survives. Only wrappers **containing** an image
- * are opened: a plain link keeps its own token, and therefore keeps the styling
- * and click handling `renderInlineToRichText` gives it.
- */
 /**
  * Every image in an inline run, at any depth, in source order.
  *
@@ -64,18 +51,22 @@ export declare function imagesOf(tokens: Token[] | undefined): Tokens.Image[];
  * while its images render as blocks beneath.
  */
 export declare function stripImages<T extends Token>(token: T): T;
-export declare function liftNestedImages(tokens: Token[]): Token[];
-/** Index of the last `image` token in an inline run, or -1 if there is none. */
-export declare function lastIndexOfImage(tokens: Token[]): number;
 /**
- * How many `Stack` children the paragraph render arm builds for an inline run.
+ * An inline run with nested images lifted to the top level, in source order.
  *
- * One child per image, plus one per *maximal run* of consecutive non-image
- * tokens — the arm merges those into a single `RichText` via `flushText`, so this
- * is not `tokens.length`. Kept in lockstep with that arm; it is what
- * `updateImageParagraph` checks to confirm the entity it was handed is the one
- * built for the old tokens.
+ * The paragraph arm splits a run into one `Stack` child per image plus one per
+ * maximal run of non-image tokens, which requires every image to be a direct
+ * member of the array it iterates. An image inside a link or an emphasis is not,
+ * so the run is flattened first.
+ *
+ * A wrapper is replaced by its children rather than dropped, so the text inside a
+ * link that also holds an image survives. Only wrappers **containing** an image
+ * are opened: a plain link keeps its own token, and therefore keeps the styling
+ * and click handling `renderInlineToRichText` gives it.
  */
+export declare function liftNestedImages(tokens: Token[]): Token[];
+/** Index of the last `image` token in an inline run, or -1 if there is none. */
+export declare function lastIndexOfImage(tokens: Token[]): number;
 /**
  * A decoding raster for one inline image, keyed by URL.
  *
@@ -123,4 +114,13 @@ export declare function ensureInlineImageRaster(src: string): InlineImageRaster;
 export declare function paintInlineImage(src: string, surface: InlineObjectSurface, box: InlineObjectBox): void;
 /** Drop every cached raster. Tests only — a decode is process-wide state. */
 export declare function clearInlineImageRasters(): void;
+/**
+ * How many `Stack` children the paragraph render arm builds for an inline run.
+ *
+ * One child per image, plus one per *maximal run* of consecutive non-image
+ * tokens — the arm merges those into a single `RichText` via `flushText`, so this
+ * is not `tokens.length`. Kept in lockstep with that arm; it is what
+ * `updateImageParagraph` checks to confirm the entity it was handed is the one
+ * built for the old tokens.
+ */
 export declare function expectedImageParagraphChildren(tokens: Token[]): number;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@vectojs/markdown",
-  "version": "0.22.0",
+  "version": "0.23.0",
   "publishConfig": {
     "access": "public"
   },
@@ -44,7 +44,7 @@
     "test:e2e": "bun e2e/blockquote-layout.e2e.ts && bun e2e/stream-controller.e2e.ts && bun e2e/lazy-math.e2e.ts && bun e2e/paragraph-image-repaint.e2e.ts && bun e2e/inline-image.e2e.ts && bun e2e/selection-fidelity.e2e.ts && bun e2e/code-atlas-dpr.e2e.ts && bun e2e/set-max-width.e2e.ts && bun e2e/block-affordances.e2e.ts && bun e2e/single-tilde-ink.e2e.ts && bun e2e/superscript-ink.e2e.ts && bun e2e/ins-mark-ink.e2e.ts && bun e2e/container-ink.e2e.ts && bun e2e/abbr-ink.e2e.ts"
   },
   "dependencies": {
-    "@vectojs/tex": "^0.1.1",
+    "@vectojs/tex": "^0.1.2",
     "marked": "^18.0.7"
   },
   "peerDependencies": {

package/dist/markdown-typography.d.ts

@@ -1,72 +0,0 @@
-/**
- * Typographic replacements: `--`/`---` to en/em dash, `...` to `…`, `(c)`/`(r)`/
- * `(tm)` to `©`/`®`/`™`, `+-` to `±`, and repeated `!`/`,` collapsing —
- * `markdown-it`'s `typographer: true` set, minus smart quotes (see below).
- *
- * Ported as a **pure text transform** rather than a new tokenizer or `marked`
- * extension, because that is what it is upstream too: `markdown-it`'s own
- * `replacements` rule runs as a `core` pass over already-tokenized `text`
- * content, not a grammar rule, and every substitution here is describable the
- * same way — a regex over a string that changes no token boundaries. Applying
- * it as the last step before a `text`-bearing span is pushed keeps this
- * completely orthogonal to every other inline arm: a bold/italic/code run's
- * content transforms identically to a plain paragraph's, because it is the same
- * function call, not a special case duplicated per arm.
- *
- * ## Off by default, unlike every other construct in this package
- *
- * `markdown-it` itself defaults `typographer` to `false`, and this mirrors
- * that rather than picking a different default for parity's own sake: the
- * transform is lossy (a real `--` a caller wanted to keep literal, e.g. a CLI
- * flag or a code-adjacent range, becomes an en dash with no way back short of
- * disabling the whole feature) and every other construct in this package
- * (subscript, superscript, ins/mark, emoji, footnotes) is instead
- * unconditionally-on syntax recognition with no lossy default to weigh.
- * `theme.typographer` (default `false`) is the gate, checked once per paragraph
- * of text collection rather than per span, so a caller who never opts in pays
- * nothing beyond the one boolean check `collectSpans` already does today for
- * `inherited`.
- *
- * ## Smart quotes are deliberately NOT ported
- *
- * `markdown-it`'s `smartquotes` rule curls straight quotes into `‘’“”` by
- * walking the FULL inline-token sequence of one block with a stack that
- * matches an opening quote to its closing partner, consulting the previous and
- * next token's own trailing/leading character across token boundaries (see
- * `references/markdown-it/lib/rules_core/smartquotes.mjs`'s `process_inlines`).
- * That is not a per-span text transform — it is a second pass over
- * `collectSpans`' entire OUTPUT array, with cross-span state (the open-quote
- * stack) and lookback/lookahead into neighboring spans' text. Porting it here
- * would mean walking `out` after the fact, which every call site of
- * `collectSpans`/`applyTypography` would have to remember to do, and getting it
- * wrong reads as a rendering defect (mismatched curly quotes) rather than a
- * missing feature. Left unimplemented; a caller wanting curled quotes still
- * gets straight ones, the same honest fallback every unsupported construct in
- * this package gets.
- */
-/**
- * Apply typographic substitutions to one run of plain text.
- *
- * Order matters and mirrors `markdown-it`'s own rule (`replace_scoped` before
- * `replace_rare`, and within the latter: `+-`, then `...`, then the
- * `?`/`!`-adjacent ellipsis correction, then `!!!!`/`,,`, then em-dash, then
- * en-dash):
- *
- * - `+-` before `...`: neither can produce the other's trigger character, so
- *   order between them is actually inert, but matching upstream's order keeps
- *   this auditable against it rather than needing its own independent proof.
- * - The em-dash pass runs before the en-dash pass. `---` is three hyphens; the
- *   en-dash patterns below both require a NON-hyphen on the dash-adjacent side
- *   (`(?=[^-]|$)` / preceded by whitespace or a non-hyphen-non-space), so `---`
- *   itself never matches either en-dash pattern regardless of order — but a
- *   FOUR-hyphen run (`----`) would: the em-dash regex only consumes exactly
- *   three of the four hyphens (`(^|[^-])---(?=[^-]|$)` requires its OWN
- *   boundary hyphens to be non-hyphen), leaving a leftover single hyphens on
- *   either side that the leftover isn't itself `--`. Verified empirically
- *   against `markdown-it`'s reference implementation that `----` and `---`
- *   both resolve to one em dash: `----` is not decomposed into em+en, and
- *   running en-dash first would have changed that (the outer pair of the four
- *   hyphens would each independently look like the START of a `--` run before
- *   the em-dash pass ever saw the middle two as a `---`).
- */
-export declare function applyTypography(text: string): string;