chore(deps-dev): upgrade eleventy 2->3 and markdown-it 13->14 in /docs#1984
Merged
Conversation
Bumps @11ty/eleventy 2.0.1 -> 3.1.6 and markdown-it 13.0.2 -> 14.2.0 (#1976). Eleventy v3 ships its named exports (EleventyHtmlBasePlugin, EleventyRenderPlugin) as ESM-only, so the top-level require() in the CommonJS config breaks on Node < 22.12. Resolved by making the config callback async and dynamic-importing those exports inside it, keeping the rest of the file CommonJS. Eleventy v3 requires Node >=18, so the docs build/deploy and lint workflows are bumped from Node 16 to Node 20 (also satisfies gitly's >=20 engine requirement). Plugins (syntaxhighlight 4.2.0, eleventy-fetch 3.0.0, eleventy-plugin-toc 1.1.5, markdown-it-emoji 2.0.2) verified compatible with v3 as-is, no bumps required. Build produces 880 files identically to v2; syntax highlighting, mermaid, and TOC all render correctly. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
gotbadger
reviewed
Jun 23, 2026
gotbadger
approved these changes
Jun 23, 2026
elsapet
commented
Jun 23, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Supersedes dependabot PR #1976 (which bumps only the two packages and would not build under eleventy v3 without the config/CI changes below).
What
@11ty/eleventy2.0.1 → 3.1.6markdown-it13.0.2 → 14.2.0docs/.eleventy.js: config callback madeasync;EleventyHtmlBasePlugin/EleventyRenderPluginmoved to a dynamicimport()inside itdocs.yml(build + Pages deploy) andlint_docs.yml(lint)Why the config change
Eleventy v3 publishes its named exports as ESM-only, so the top-level
require("@11ty/eleventy")throws on Node < 22.12. Rather than convert the whole CommonJS config (and all the localrequired modules) to ESM, only those two exports are dynamic-import()ed inside the now-asynccallback — the eleventy-recommended minimal fix.Why Node 20
Eleventy v3 requires Node ≥18;
gitlywants ≥20. Node 20 (active LTS) satisfies both.Minimal churn
syntaxhighlight(4.2.0),eleventy-fetch(3.0.0),eleventy-plugin-toc(1.1.5) andmarkdown-it-emoji(2.0.2) are all compatible with v3 unchanged — no extra bumps, no markdown-it-emoji v3 import migration needed.Verification
npm ci+npm run buildon Node 20-equivalent → exit 0, 880 files on v3.1.6 (identical count to v2), no warnings/errorsnpm run lint→ exit 0_sitechecked: syntax highlighting (491 pages), mermaid (1), TOC (498) all render and coexist; 0 unrendered template/shortcode tags🤖 Generated with Claude Code