chore(deps): Bump asciidoctor from 4.0.8 to 4.0.10 in the npm-minor-patch group across 1 directory

[dependabot]

Bumps the npm-minor-patch group with 1 update in the / directory: asciidoctor.

Updates asciidoctor from 4.0.8 to 4.0.10

Release notes

Sourced from asciidoctor's releases.

v4.0.10

Summary

Release meta

Released on: 2026-08-17 Released by: ggrossetie Published by: GitHub

Logs: full diff

Changelog

Bug Fixes

• Fix the inline pass:[...] macro escaping its content instead of passing it through unmodified when no explicit substitution list is given, e.g. pass:[<u>underlined</u>] rendered as <u&gt;underlined</u&gt; instead of <u>underlined</u>. The passthrough’s subs was left undefined, which fell through to applySubs()’s NORMAL_SUBS` default parameter instead of the intended "no substitutions" behavior (#1870)
• Fix a footnote inside a list item or table cell not advancing the footnote counter, causing a subsequent footnote elsewhere in the document to reuse the same number and id (invalid HTML, and the later footnote reference would link to the earlier definition). List item and table cell text is substituted eagerly, ahead of normal body conversion, and the footnote counter was unconditionally reset afterwards; it now carries forward into conversion so later footnotes continue numbering from where these left off (#1871)

v4.0.9

Summary

Release meta

Released on: 2026-08-16 Released by: ggrossetie Published by: GitHub

Logs: full diff

Changelog

Bug Fixes

• Fix the extension DSL this types (BlockProcessorDslInterface, BlockMacroProcessorDslInterface, InlineMacroProcessorDslInterface, and the document-processor DSLs for preprocessors, tree processors, postprocessors, include processors, and docinfo processors) missing the node-builder helpers -- createSection, createBlock, createList, createListItem, createImageBlock, createInline, parseContent, parseAttributes, and the createBlock/createInline shorthands (createParagraph, createOpenBlock, createExampleBlock, createPassBlock, createListingBlock, createLiteralBlock, createAnchor, createInlinePass) -- even though all of them are available at runtime on the bound processor instance, since every processor type shares the same Processor base class (matching Ruby’s Asciidoctor::Extensions::Processor)
• Fix JSDoc Document type references across abstract_node.js, extensions.js, parser.js, syntax_highlighter.js, and table.js (and the corresponding generated .d.ts files) resolving to the ambient DOM Document type instead of Asciidoctor’s own Document class from document.js. None of those source files imported Document, so TypeScript resolved the unqualified name to lib.dom.d.ts — getDocument(), extension processor callbacks (Preprocessor#process(), TreeProcessor#process(), etc.), Parser methods, SyntaxHighlighterBase methods, and Table.Cell#getInnerDocument() were all typed against the browser DOM document rather than the Asciidoctor document, silently defeating type checking on any code calling Asciidoctor Document methods on the result
• Fix logging.js logging a spurious CORS error to the console in some browsers (e.g. Firefox) on first use. The per-execution logger context lazily probes for node:async_hooks and falls back to null when unavailable, but the dynamic import('node:async_hooks') itself was still attempted in the browser, where it is treated as a cross-origin fetch and rejected -- caught safely, but still logged by the browser regardless. The import is now skipped entirely when process is undefined (i.e. outside Node.js)

Infrastructure

• Add compile-only type tests (test/types/document_type.test-d.ts) guarding against the Document DOM-leak regression above, covering AbstractNode#getDocument(), Preprocessor/TreeProcessor/Postprocessor/IncludeProcessor/DocinfoProcessor’s process()/handles(), Registry#activate(), and SyntaxHighlighterBase’s docinfo()/writeStylesheet()/writeStylesheetToDisk()

Changelog

Sourced from asciidoctor's changelog.

== v4.0.10 (2026-08-17)

Bug Fixes::

• Fix the inline pass:[...] macro escaping its content instead of passing it through unmodified when no explicit substitution list is given, e.g. pass:[<u>underlined</u>] rendered as <u>underlined</u> instead of <u>underlined</u>. The passthrough's subs was left undefined, which fell through to applySubs()'s NORMAL_SUBS default parameter instead of the intended "no substitutions" behavior (asciidoctor/asciidoctor.js#1870)
• Fix a footnote inside a list item or table cell not advancing the footnote counter, causing a subsequent footnote elsewhere in the document to reuse the same number and id (invalid HTML, and the later footnote reference would link to the earlier definition). List item and table cell text is substituted eagerly, ahead of normal body conversion, and the footnote counter was unconditionally reset afterwards; it now carries forward into conversion so later footnotes continue numbering from where these left off (asciidoctor/asciidoctor.js#1871)

== v4.0.9 (2026-08-16)

Bug Fixes::

• Fix the extension DSL this types (BlockProcessorDslInterface, BlockMacroProcessorDslInterface, InlineMacroProcessorDslInterface, and the document-processor DSLs for preprocessors, tree processors, postprocessors, include processors, and docinfo processors) missing the node-builder helpers -- createSection, createBlock, createList, createListItem, createImageBlock, createInline, parseContent, parseAttributes, and the createBlock/createInline shorthands (createParagraph, createOpenBlock, createExampleBlock, createPassBlock, createListingBlock, createLiteralBlock, createAnchor, createInlinePass) -- even though all of them are available at runtime on the bound processor instance, since every processor type shares the same Processor base class (matching Ruby's Asciidoctor::Extensions::Processor)
• Fix JSDoc Document type references across abstract_node.js, extensions.js, parser.js, syntax_highlighter.js, and table.js (and the corresponding generated .d.ts files) resolving to the ambient DOM Document type instead of Asciidoctor's own Document class from document.js. None of those source files imported Document, so TypeScript resolved the unqualified name to lib.dom.d.ts — getDocument(), extension processor callbacks (Preprocessor#process(), TreeProcessor#process(), etc.), Parser methods, SyntaxHighlighterBase methods, and Table.Cell#getInnerDocument() were all typed against the browser DOM document rather than the Asciidoctor document, silently defeating type checking on any code calling Asciidoctor Document methods on the result
• Fix logging.js logging a spurious CORS error to the console in some browsers (e.g. Firefox) on first use. The per-execution logger context lazily probes for node:async_hooks and falls back to null when unavailable, but the dynamic import('node:async_hooks') itself was still attempted in the browser, where it is treated as a cross-origin fetch and rejected -- caught safely, but still logged by the browser regardless. The import is now skipped entirely when process is undefined (i.e. outside Node.js)

Infrastructure::

• Add compile-only type tests (test/types/document_type.test-d.ts) guarding against the Document DOM-leak regression above, covering AbstractNode#getDocument(), Preprocessor/TreeProcessor/Postprocessor/IncludeProcessor/DocinfoProcessor's process()/handles(), Registry#activate(), and SyntaxHighlighterBase's docinfo()/writeStylesheet()/writeStylesheetToDisk()

Commits

• af405a0 4.0.10
• 28ccd0c fix(core): footnote inside list item or table cell not advancing counter
• 3b71cf0 fix(core): pass:[] inline macro escapes content instead of passing it through
• 4077572 4.0.9
• 4303dfd fix(core): expose node-builder helpers on every extension DSL, not just Block...
• 867131a test(core): guard against Document JSDoc resolving to DOM Document
• b70cade fix(core): resolve remaining Document type refs to Asciidoctor's Document
• 2339d09 fix(core): resolve Document type to Asciidoctor's Document, not DOM
• d19de35 fix(core): skip node:async_hooks import outside Node.js
• See full diff in compare view

[dependabot]

This pull request was built based on a group rule. Closing it will not ignore any of these versions in future pull requests.

To ignore these dependencies, configure ignore rules in dependabot.yml

[DeepDiver1975]

@dependabot rebase

[DeepDiver1975]

@dependabot rebase