@savvy-web/silk 1.3.11 → 2.1.0

package/packages/silk-effects/dist/dev/pkg/changesets/utils/remark-pipeline.cjs

@@ -1,81 +0,0 @@
-const require_index = require('../../../../../../../node_modules/.pnpm/remark-gfm@4.0.1/node_modules/remark-gfm/lib/index.cjs');
-const require_index$1 = require('../../../../../../../node_modules/.pnpm/remark-parse@11.0.0/node_modules/remark-parse/lib/index.cjs');
-const require_index$2 = require('../../../../../../../node_modules/.pnpm/remark-stringify@11.0.0/node_modules/remark-stringify/lib/index.cjs');
-const require_index$3 = require('../../../../../../../node_modules/.pnpm/unified@11.0.5/node_modules/unified/lib/index.cjs');
-
-//#region ../silk-effects/dist/dev/pkg/changesets/utils/remark-pipeline.js
-/**
-* Create a unified processor configured with remark-parse, remark-gfm,
-* and remark-stringify.
-*
-* @remarks
-* Each call creates a fresh processor instance. The plugin chain is:
-* 1. `remark-parse` — markdown to MDAST
-* 2. `remark-gfm` — GitHub Flavored Markdown extensions (tables, etc.)
-* 3. `remark-stringify` — MDAST back to markdown
-*
-* @privateRemarks
-* Return type is intentionally inferred because the unified `Processor`
-* generic signature is complex and parameterized by the plugin chain.
-*
-* @returns A configured unified processor
-*
-* @internal
-*/
-function createRemarkProcessor() {
-	return require_index$3.unified().use(require_index$1.default).use(require_index.default).use(require_index$2.default);
-}
-/**
-* Parse a markdown string into an MDAST AST synchronously.
-*
-* @remarks
-* Uses {@link createRemarkProcessor} internally. The returned tree
-* includes GFM extensions (tables, strikethrough, etc.) thanks to
-* the remark-gfm plugin.
-*
-* @param content - Raw markdown string
-* @returns The parsed MDAST root node
-*
-* @example
-* ```typescript
-* import { parseMarkdown } from "../utils/remark-pipeline.js";
-*
-* const tree = parseMarkdown("## Version 1.0.0\n\nInitial release.");
-* // tree.type === "root"
-* // tree.children[0].type === "heading"
-* ```
-*
-* @internal
-*/
-function parseMarkdown(content) {
-	return createRemarkProcessor().parse(content);
-}
-/**
-* Stringify an MDAST AST back to a markdown string synchronously.
-*
-* @remarks
-* Uses {@link createRemarkProcessor} internally. GFM constructs
-* (tables, etc.) are serialized correctly thanks to the remark-gfm plugin.
-*
-* @param tree - The MDAST root node
-* @returns The serialized markdown string
-*
-* @example
-* ```typescript
-* import { parseMarkdown, stringifyMarkdown } from "../utils/remark-pipeline.js";
-*
-* const tree = parseMarkdown("# Hello\n\nWorld.");
-* const md = stringifyMarkdown(tree);
-* // "# Hello\n\nWorld.\n"
-* ```
-*
-* @internal
-*/
-function stringifyMarkdown(tree) {
-	return createRemarkProcessor().stringify(tree);
-}
-
-//#endregion
-exports.createRemarkProcessor = createRemarkProcessor;
-exports.parseMarkdown = parseMarkdown;
-exports.stringifyMarkdown = stringifyMarkdown;

package/packages/silk-effects/dist/dev/pkg/changesets/utils/remark-pipeline.js

@@ -1,79 +0,0 @@
-import remarkGfm from "../../../../../../../node_modules/.pnpm/remark-gfm@4.0.1/node_modules/remark-gfm/lib/index.js";
-import remarkParse from "../../../../../../../node_modules/.pnpm/remark-parse@11.0.0/node_modules/remark-parse/lib/index.js";
-import remarkStringify from "../../../../../../../node_modules/.pnpm/remark-stringify@11.0.0/node_modules/remark-stringify/lib/index.js";
-import { unified } from "../../../../../../../node_modules/.pnpm/unified@11.0.5/node_modules/unified/lib/index.js";
-
-//#region ../silk-effects/dist/dev/pkg/changesets/utils/remark-pipeline.js
-/**
-* Create a unified processor configured with remark-parse, remark-gfm,
-* and remark-stringify.
-*
-* @remarks
-* Each call creates a fresh processor instance. The plugin chain is:
-* 1. `remark-parse` — markdown to MDAST
-* 2. `remark-gfm` — GitHub Flavored Markdown extensions (tables, etc.)
-* 3. `remark-stringify` — MDAST back to markdown
-*
-* @privateRemarks
-* Return type is intentionally inferred because the unified `Processor`
-* generic signature is complex and parameterized by the plugin chain.
-*
-* @returns A configured unified processor
-*
-* @internal
-*/
-function createRemarkProcessor() {
-	return unified().use(remarkParse).use(remarkGfm).use(remarkStringify);
-}
-/**
-* Parse a markdown string into an MDAST AST synchronously.
-*
-* @remarks
-* Uses {@link createRemarkProcessor} internally. The returned tree
-* includes GFM extensions (tables, strikethrough, etc.) thanks to
-* the remark-gfm plugin.
-*
-* @param content - Raw markdown string
-* @returns The parsed MDAST root node
-*
-* @example
-* ```typescript
-* import { parseMarkdown } from "../utils/remark-pipeline.js";
-*
-* const tree = parseMarkdown("## Version 1.0.0\n\nInitial release.");
-* // tree.type === "root"
-* // tree.children[0].type === "heading"
-* ```
-*
-* @internal
-*/
-function parseMarkdown(content) {
-	return createRemarkProcessor().parse(content);
-}
-/**
-* Stringify an MDAST AST back to a markdown string synchronously.
-*
-* @remarks
-* Uses {@link createRemarkProcessor} internally. GFM constructs
-* (tables, etc.) are serialized correctly thanks to the remark-gfm plugin.
-*
-* @param tree - The MDAST root node
-* @returns The serialized markdown string
-*
-* @example
-* ```typescript
-* import { parseMarkdown, stringifyMarkdown } from "../utils/remark-pipeline.js";
-*
-* const tree = parseMarkdown("# Hello\n\nWorld.");
-* const md = stringifyMarkdown(tree);
-* // "# Hello\n\nWorld.\n"
-* ```
-*
-* @internal
-*/
-function stringifyMarkdown(tree) {
-	return createRemarkProcessor().stringify(tree);
-}
-
-//#endregion
-export { createRemarkProcessor, parseMarkdown, stringifyMarkdown };

package/packages/silk-effects/dist/dev/pkg/changesets/utils/section-parser.cjs

@@ -1,94 +0,0 @@
-const require_index = require('../categories/index.cjs');
-const require_index$1 = require('../../../../../../../node_modules/.pnpm/mdast-util-to-string@4.0.0/node_modules/mdast-util-to-string/lib/index.cjs');
-const require_remark_pipeline = require('./remark-pipeline.cjs');
-
-//#region ../silk-effects/dist/dev/pkg/changesets/utils/section-parser.js
-/**
-* Parse a changeset summary into structured sections.
-*
-* @remarks
-* The algorithm works in three steps:
-* 1. Parse the summary markdown into an MDAST tree via {@link parseMarkdown}
-* 2. Scan `tree.children` for h2 (`depth === 2`) headings, recording their
-*    indices
-* 3. For each h2, extract the heading text, resolve it to a
-*    {@link SectionCategory} via `fromHeading()`, and collect all nodes
-*    between this h2 and the next h2 (or end of document) as the section
-*    content
-*
-* If the summary contains h2 (`##`) headings, they are mapped to categories
-* via `fromHeading()`. Content between headings becomes the section content.
-* Content before the first h2 becomes the preamble.
-*
-* If no h2 headings are present, the entire content is returned as the preamble
-* with an empty sections array (backward-compatible flat-text mode).
-*
-* Unknown headings (those not recognized by `fromHeading()`) are silently
-* skipped; validation of heading names is the responsibility of Layer 1
-* (remark-lint).
-*
-* @param summary - The changeset summary markdown
-* @returns Parsed sections and optional preamble
-*
-* @example
-* ```typescript
-* import { parseChangesetSections } from "../utils/section-parser.js";
-*
-* const result = parseChangesetSections("## Features\n\n- New API\n\n## Bug Fixes\n\n- Fixed crash");
-* // result.sections.length === 2
-* // result.sections[0].category === "Features"
-* // result.preamble === undefined
-* ```
-*
-* @internal
-*/
-function parseChangesetSections(summary) {
-	const tree = require_remark_pipeline.parseMarkdown(summary);
-	const h2Indices = [];
-	for (let i = 0; i < tree.children.length; i++) {
-		const node = tree.children[i];
-		if (node.type === "heading" && node.depth === 2) h2Indices.push(i);
-	}
-	if (h2Indices.length === 0) return {
-		preamble: summary.trim(),
-		sections: []
-	};
-	const result = { sections: [] };
-	if (h2Indices[0] > 0) result.preamble = stringifyAstSlice(tree.children.slice(0, h2Indices[0]));
-	for (let i = 0; i < h2Indices.length; i++) {
-		const headingIndex = h2Indices[i];
-		const headingNode = tree.children[headingIndex];
-		const headingText = require_index$1.toString(headingNode);
-		const nextIndex = i + 1 < h2Indices.length ? h2Indices[i + 1] : tree.children.length;
-		const content = stringifyAstSlice(tree.children.slice(headingIndex + 1, nextIndex));
-		const category = require_index.fromHeading(headingText);
-		if (category) result.sections.push({
-			category,
-			heading: headingText,
-			content
-		});
-	}
-	return result;
-}
-/**
-* Stringify a slice of MDAST nodes back to markdown.
-*
-* @remarks
-* Wraps the nodes in a synthetic root node and delegates to
-* {@link stringifyMarkdown}. Returns an empty string for empty slices.
-*
-* @param nodes - Array of MDAST content nodes
-* @returns Trimmed markdown string, or empty string if no nodes
-*
-* @internal
-*/
-function stringifyAstSlice(nodes) {
-	if (nodes.length === 0) return "";
-	return require_remark_pipeline.stringifyMarkdown({
-		type: "root",
-		children: nodes
-	}).trim();
-}
-
-//#endregion
-exports.parseChangesetSections = parseChangesetSections;

package/packages/silk-effects/dist/dev/pkg/changesets/utils/section-parser.js

@@ -1,94 +0,0 @@
-import { fromHeading } from "../categories/index.js";
-import { toString } from "../../../../../../../node_modules/.pnpm/mdast-util-to-string@4.0.0/node_modules/mdast-util-to-string/lib/index.js";
-import { parseMarkdown, stringifyMarkdown } from "./remark-pipeline.js";
-
-//#region ../silk-effects/dist/dev/pkg/changesets/utils/section-parser.js
-/**
-* Parse a changeset summary into structured sections.
-*
-* @remarks
-* The algorithm works in three steps:
-* 1. Parse the summary markdown into an MDAST tree via {@link parseMarkdown}
-* 2. Scan `tree.children` for h2 (`depth === 2`) headings, recording their
-*    indices
-* 3. For each h2, extract the heading text, resolve it to a
-*    {@link SectionCategory} via `fromHeading()`, and collect all nodes
-*    between this h2 and the next h2 (or end of document) as the section
-*    content
-*
-* If the summary contains h2 (`##`) headings, they are mapped to categories
-* via `fromHeading()`. Content between headings becomes the section content.
-* Content before the first h2 becomes the preamble.
-*
-* If no h2 headings are present, the entire content is returned as the preamble
-* with an empty sections array (backward-compatible flat-text mode).
-*
-* Unknown headings (those not recognized by `fromHeading()`) are silently
-* skipped; validation of heading names is the responsibility of Layer 1
-* (remark-lint).
-*
-* @param summary - The changeset summary markdown
-* @returns Parsed sections and optional preamble
-*
-* @example
-* ```typescript
-* import { parseChangesetSections } from "../utils/section-parser.js";
-*
-* const result = parseChangesetSections("## Features\n\n- New API\n\n## Bug Fixes\n\n- Fixed crash");
-* // result.sections.length === 2
-* // result.sections[0].category === "Features"
-* // result.preamble === undefined
-* ```
-*
-* @internal
-*/
-function parseChangesetSections(summary) {
-	const tree = parseMarkdown(summary);
-	const h2Indices = [];
-	for (let i = 0; i < tree.children.length; i++) {
-		const node = tree.children[i];
-		if (node.type === "heading" && node.depth === 2) h2Indices.push(i);
-	}
-	if (h2Indices.length === 0) return {
-		preamble: summary.trim(),
-		sections: []
-	};
-	const result = { sections: [] };
-	if (h2Indices[0] > 0) result.preamble = stringifyAstSlice(tree.children.slice(0, h2Indices[0]));
-	for (let i = 0; i < h2Indices.length; i++) {
-		const headingIndex = h2Indices[i];
-		const headingNode = tree.children[headingIndex];
-		const headingText = toString(headingNode);
-		const nextIndex = i + 1 < h2Indices.length ? h2Indices[i + 1] : tree.children.length;
-		const content = stringifyAstSlice(tree.children.slice(headingIndex + 1, nextIndex));
-		const category = fromHeading(headingText);
-		if (category) result.sections.push({
-			category,
-			heading: headingText,
-			content
-		});
-	}
-	return result;
-}
-/**
-* Stringify a slice of MDAST nodes back to markdown.
-*
-* @remarks
-* Wraps the nodes in a synthetic root node and delegates to
-* {@link stringifyMarkdown}. Returns an empty string for empty slices.
-*
-* @param nodes - Array of MDAST content nodes
-* @returns Trimmed markdown string, or empty string if no nodes
-*
-* @internal
-*/
-function stringifyAstSlice(nodes) {
-	if (nodes.length === 0) return "";
-	return stringifyMarkdown({
-		type: "root",
-		children: nodes
-	}).trim();
-}
-
-//#endregion
-export { parseChangesetSections };

package/packages/silk-effects/dist/dev/pkg/changesets/utils/strip-frontmatter.cjs

@@ -1,47 +0,0 @@
-
-//#region ../silk-effects/dist/dev/pkg/changesets/utils/strip-frontmatter.js
-/**
-* Utility for stripping YAML frontmatter from changeset files.
-*
-* @remarks
-* Changeset `.md` files produced by `\@changesets/cli` contain YAML
-* frontmatter (delimited by `---`) specifying which packages are
-* affected and their version bump types. This frontmatter must be
-* removed before remark-lint processing, as remark-parse does not
-* handle YAML frontmatter natively without `remark-frontmatter`.
-*
-* The regex used is non-greedy (`[\s\S]*?`) to match only the first
-* frontmatter block and avoid stripping content after a second `---`
-* delimiter that might appear in the document body.
-*
-* @see {@link ChangesetLinter} for the public API that uses frontmatter
-*   stripping during changeset validation
-*
-* @internal
-*/
-/**
-* Strip leading YAML frontmatter from a markdown string.
-*
-* Removes the `---\n...\n---\n` block at the start of the content.
-* If no frontmatter is present, the content is returned as-is.
-*
-* @param content - Raw markdown string potentially containing frontmatter
-* @returns The markdown content with frontmatter removed
-*
-* @example
-* ```typescript
-* import { stripFrontmatter } from "../utils/strip-frontmatter.js";
-*
-* const raw = "---\n\"pkg\": minor\n---\n\n## Features\n\n- New API";
-* const body = stripFrontmatter(raw);
-* // "\n## Features\n\n- New API"
-* ```
-*
-* @internal
-*/
-function stripFrontmatter(content) {
-	return content.replace(/^---\n[\s\S]*?\n---\n?/, "");
-}
-
-//#endregion
-exports.stripFrontmatter = stripFrontmatter;

package/packages/silk-effects/dist/dev/pkg/changesets/utils/strip-frontmatter.js

@@ -1,46 +0,0 @@
-//#region ../silk-effects/dist/dev/pkg/changesets/utils/strip-frontmatter.js
-/**
-* Utility for stripping YAML frontmatter from changeset files.
-*
-* @remarks
-* Changeset `.md` files produced by `\@changesets/cli` contain YAML
-* frontmatter (delimited by `---`) specifying which packages are
-* affected and their version bump types. This frontmatter must be
-* removed before remark-lint processing, as remark-parse does not
-* handle YAML frontmatter natively without `remark-frontmatter`.
-*
-* The regex used is non-greedy (`[\s\S]*?`) to match only the first
-* frontmatter block and avoid stripping content after a second `---`
-* delimiter that might appear in the document body.
-*
-* @see {@link ChangesetLinter} for the public API that uses frontmatter
-*   stripping during changeset validation
-*
-* @internal
-*/
-/**
-* Strip leading YAML frontmatter from a markdown string.
-*
-* Removes the `---\n...\n---\n` block at the start of the content.
-* If no frontmatter is present, the content is returned as-is.
-*
-* @param content - Raw markdown string potentially containing frontmatter
-* @returns The markdown content with frontmatter removed
-*
-* @example
-* ```typescript
-* import { stripFrontmatter } from "../utils/strip-frontmatter.js";
-*
-* const raw = "---\n\"pkg\": minor\n---\n\n## Features\n\n- New API";
-* const body = stripFrontmatter(raw);
-* // "\n## Features\n\n- New API"
-* ```
-*
-* @internal
-*/
-function stripFrontmatter(content) {
-	return content.replace(/^---\n[\s\S]*?\n---\n?/, "");
-}
-
-//#endregion
-export { stripFrontmatter };

package/packages/silk-effects/dist/dev/pkg/changesets/utils/version-blocks.cjs

@@ -1,110 +0,0 @@
-const require_index = require('../../../../../../../node_modules/.pnpm/mdast-util-to-string@4.0.0/node_modules/mdast-util-to-string/lib/index.cjs');
-
-//#region ../silk-effects/dist/dev/pkg/changesets/utils/version-blocks.js
-/**
-* Extract all version blocks from a CHANGELOG AST.
-*
-* @remarks
-* Scans `tree.children` linearly for h2-level headings. Each h2 starts
-* a new version block whose content extends to the next h2 or the end
-* of the document. The `endIndex` of each block is adjusted in a second
-* pass to stop at the next block's `headingIndex`.
-*
-* h1 headings (typically the package name) are ignored and do not
-* create version blocks.
-*
-* @param tree - The MDAST root node of a CHANGELOG document
-* @returns Array of version blocks in document order
-*
-* @example
-* ```typescript
-* import { getVersionBlocks } from "../utils/version-blocks.js";
-* import { parseMarkdown } from "../utils/remark-pipeline.js";
-*
-* const tree = parseMarkdown("# my-pkg\n\n## 1.1.0\n\nChanges.\n\n## 1.0.0\n\nInitial.");
-* const blocks = getVersionBlocks(tree);
-* // blocks.length === 2
-* // blocks[0] covers "## 1.1.0" section
-* // blocks[1] covers "## 1.0.0" section
-* ```
-*
-* @internal
-*/
-function getVersionBlocks(tree) {
-	const blocks = [];
-	for (let i = 0; i < tree.children.length; i++) {
-		const node = tree.children[i];
-		if (node.type === "heading" && node.depth === 2) blocks.push({
-			headingIndex: i,
-			startIndex: i + 1,
-			endIndex: tree.children.length
-		});
-	}
-	for (let i = 0; i < blocks.length - 1; i++) blocks[i].endIndex = blocks[i + 1].headingIndex;
-	return blocks;
-}
-/**
-* Extract h3 sections within a version block.
-*
-* @remarks
-* Iterates over the children of the given version block (from
-* `block.startIndex` to `block.endIndex`). Each h3 heading starts
-* a new section, and subsequent non-heading nodes are collected
-* into that section's `contentNodes` array until the next h3 or
-* the end of the block.
-*
-* Nodes before the first h3 within the block (e.g., a version
-* summary paragraph) are not included in any section.
-*
-* @param tree - The MDAST root node of a CHANGELOG document
-* @param block - The version block to extract sections from
-* @returns Array of sections in document order
-*
-* @example
-* ```typescript
-* import { getVersionBlocks, getBlockSections } from "../utils/version-blocks.js";
-* import { parseMarkdown } from "../utils/remark-pipeline.js";
-*
-* const tree = parseMarkdown("## 1.0.0\n\n### Features\n\n- New API\n\n### Bug Fixes\n\n- Fixed crash");
-* const blocks = getVersionBlocks(tree);
-* const sections = getBlockSections(tree, blocks[0]);
-* // sections.length === 2
-* // sections[0].heading text === "Features"
-* ```
-*
-* @internal
-*/
-function getBlockSections(tree, block) {
-	const sections = [];
-	for (let i = block.startIndex; i < block.endIndex; i++) {
-		const node = tree.children[i];
-		if (node.type === "heading" && node.depth === 3) sections.push({
-			heading: node,
-			headingIndex: i,
-			contentNodes: []
-		});
-		else if (sections.length > 0) sections[sections.length - 1].contentNodes.push(node);
-	}
-	return sections;
-}
-/**
-* Get the plain text content of a heading node.
-*
-* @remarks
-* Delegates to `mdast-util-to-string` to extract concatenated text
-* from all inline children of the heading (handling bold, italic,
-* code spans, etc.).
-*
-* @param heading - The MDAST heading node
-* @returns The heading text content as a plain string
-*
-* @internal
-*/
-function getHeadingText(heading) {
-	return require_index.toString(heading);
-}
-
-//#endregion
-exports.getBlockSections = getBlockSections;
-exports.getHeadingText = getHeadingText;
-exports.getVersionBlocks = getVersionBlocks;

package/packages/silk-effects/dist/dev/pkg/changesets/utils/version-blocks.js

@@ -1,108 +0,0 @@
-import { toString } from "../../../../../../../node_modules/.pnpm/mdast-util-to-string@4.0.0/node_modules/mdast-util-to-string/lib/index.js";
-
-//#region ../silk-effects/dist/dev/pkg/changesets/utils/version-blocks.js
-/**
-* Extract all version blocks from a CHANGELOG AST.
-*
-* @remarks
-* Scans `tree.children` linearly for h2-level headings. Each h2 starts
-* a new version block whose content extends to the next h2 or the end
-* of the document. The `endIndex` of each block is adjusted in a second
-* pass to stop at the next block's `headingIndex`.
-*
-* h1 headings (typically the package name) are ignored and do not
-* create version blocks.
-*
-* @param tree - The MDAST root node of a CHANGELOG document
-* @returns Array of version blocks in document order
-*
-* @example
-* ```typescript
-* import { getVersionBlocks } from "../utils/version-blocks.js";
-* import { parseMarkdown } from "../utils/remark-pipeline.js";
-*
-* const tree = parseMarkdown("# my-pkg\n\n## 1.1.0\n\nChanges.\n\n## 1.0.0\n\nInitial.");
-* const blocks = getVersionBlocks(tree);
-* // blocks.length === 2
-* // blocks[0] covers "## 1.1.0" section
-* // blocks[1] covers "## 1.0.0" section
-* ```
-*
-* @internal
-*/
-function getVersionBlocks(tree) {
-	const blocks = [];
-	for (let i = 0; i < tree.children.length; i++) {
-		const node = tree.children[i];
-		if (node.type === "heading" && node.depth === 2) blocks.push({
-			headingIndex: i,
-			startIndex: i + 1,
-			endIndex: tree.children.length
-		});
-	}
-	for (let i = 0; i < blocks.length - 1; i++) blocks[i].endIndex = blocks[i + 1].headingIndex;
-	return blocks;
-}
-/**
-* Extract h3 sections within a version block.
-*
-* @remarks
-* Iterates over the children of the given version block (from
-* `block.startIndex` to `block.endIndex`). Each h3 heading starts
-* a new section, and subsequent non-heading nodes are collected
-* into that section's `contentNodes` array until the next h3 or
-* the end of the block.
-*
-* Nodes before the first h3 within the block (e.g., a version
-* summary paragraph) are not included in any section.
-*
-* @param tree - The MDAST root node of a CHANGELOG document
-* @param block - The version block to extract sections from
-* @returns Array of sections in document order
-*
-* @example
-* ```typescript
-* import { getVersionBlocks, getBlockSections } from "../utils/version-blocks.js";
-* import { parseMarkdown } from "../utils/remark-pipeline.js";
-*
-* const tree = parseMarkdown("## 1.0.0\n\n### Features\n\n- New API\n\n### Bug Fixes\n\n- Fixed crash");
-* const blocks = getVersionBlocks(tree);
-* const sections = getBlockSections(tree, blocks[0]);
-* // sections.length === 2
-* // sections[0].heading text === "Features"
-* ```
-*
-* @internal
-*/
-function getBlockSections(tree, block) {
-	const sections = [];
-	for (let i = block.startIndex; i < block.endIndex; i++) {
-		const node = tree.children[i];
-		if (node.type === "heading" && node.depth === 3) sections.push({
-			heading: node,
-			headingIndex: i,
-			contentNodes: []
-		});
-		else if (sections.length > 0) sections[sections.length - 1].contentNodes.push(node);
-	}
-	return sections;
-}
-/**
-* Get the plain text content of a heading node.
-*
-* @remarks
-* Delegates to `mdast-util-to-string` to extract concatenated text
-* from all inline children of the heading (handling bold, italic,
-* code spans, etc.).
-*
-* @param heading - The MDAST heading node
-* @returns The heading text content as a plain string
-*
-* @internal
-*/
-function getHeadingText(heading) {
-	return toString(heading);
-}
-
-//#endregion
-export { getBlockSections, getHeadingText, getVersionBlocks };