eleventy Files

Try it out in your project

npm install @11ty/eleventy@latest

Read more about getting started with Eleventy or why you should use Eleventy.

• v3.1.0 Issue Milestone: https://github.com/11ty/eleventy/milestone/47?closed=1
• Compare with v3.0.0: https://github.com/11ty/eleventy/compare/v3.0.0...v3.1.0

What’s new?

• Support for Import Attributes [#3580] e.g. import data from './data.json' with { type: 'json' };, see https://github.com/11ty/eleventy-dependency-tree-esm/issues/2 and https://github.com/11ty/eleventy-dependency-tree-esm/issues/4
• Build performance improvements over v3.0.0 in https://github.com/11ty/eleventy/pull/3493
  • Improve build performance ~50ms (dynamic dev server import only on --serve) by @boehs in https://github.com/11ty/eleventy/pull/3689
• Adds html-relative Passthrough Copy mode for relative asset references in HTML. Learn more at https://github.com/11ty/eleventy/pull/3573 (from issue [#3552])
• A whole bunch of Dev Server updates and fixes, most notably https://github.com/11ty/eleventy-dev-server/releases/tag/v2.0.7
• Add subpath export for UserConfig type definitions (#3460) by @noelforte in https://github.com/11ty/eleventy/pull/3562
• IdAttribute plugin has checkDuplicates option (always enabled by default, now allows you to disable) [#3560] Docs: https://www.11ty.dev/docs/plugins/id-attribute/#with-options
• Error messaging improvements:
  • Improved error messaging when attempting to link to a permalink: false template (in the HTML <base> plugin) [#3503]
  • Better errors with Custom template types with non-string permalink values: [#3472]
  • Improved error messaging with syntax errors in .11ty.js files [#3571]
  • Improved require(esm) error messaging to reflect proper support in Node v22.12 [#3568]
  • Error stack improvements by @noelforte in https://github.com/11ty/eleventy/pull/3572

Bug fixes

• Bug fix for returning non-traditional data with eleventyConfig.addCollection API [#3467]
• Internals: consolidates TemplateMap with Dependency Graph for more accurate build order during incremental builds (fixing unrendered template errors) [#3410] (Fair warning: this was a big change!)
• Fix duplicate permaink error on Windows after file delete and re-add [#3631]
• Fix (and better error messaging) for link.slice is not a function errors when using function permalinks [#3472] [#3619]
• Improvements to bundler-friendiness of imports (using Programmatic API in serverless contexts) [#3656]
• Fix when using eleventyConfig.setUseTemplateCache(false); and 11ty.js JavaScript templates [#3667]
• Fix for passthrough copy output locations during incremental builds [#3285]
• Check Error.cause for TemplateContentPrematureUseError when rendering by @noelforte in https://github.com/11ty/eleventy/pull/3651
• Fix dateValue.toLowerCase() is not a function error when using addDateParsing API [#3674]
• Improvements to engine consistency (improved use of Nunjucks cache) [#3736]
• Fixes eleventy.templateModified listeners warning [#3735]
• Fixes for bugs with merging Arrays in eleventyComputed. Arrays are now treated as a single entity when merging over non-computed data. Arrays will still be merged in the data cascade from multiple eleventyComputed entries. [#3728]
• Fix bug with collection definition on subsequent builds [#3711]
• HtmlBasePlugin: Fix confusing error message by @noelleleigh in https://github.com/11ty/eleventy/pull/3709
• Fix import-related error with CommonJS modules in Node 23 by @vrugtehagel in https://github.com/11ty/eleventy/pull/3519 [#3518]
• Fix for InputPathToUrl plugin to support unencoded paths with spaces [#3559] [#3583]

Dependency Watch

• Bumps liquidjs dependency to 10.21.0 (from 10.17.0)
• Removes rifraf dependency by @jeffalo [#3622] [#3673]
• A bunch of improvements from @e18e org folks! Upstream issue: https://github.com/e18e/ecosystem-issues/issues/164
  • Dependency optimization by @outslept in https://github.com/11ty/eleventy/pull/3715
  • Replace glob packages with lighter alternatives – fast-glob + is-glob -> tinyglobby, micromatch -> picomatch by @pralkarz in https://github.com/11ty/eleventy/pull/3680

Major Upgrades

• @11ty/dependency-tree from v3 to v4 (bumps to Node 18+) https://github.com/11ty/eleventy-dependency-tree/releases/tag/v4.0.0
• @11ty/dependency-tree-esm from v1 to v2 (bumps to Node 18+) https://github.com/11ty/eleventy-dependency-tree-esm/releases/tag/v2.0.0
• @11ty/eleventy-utils from v1 to v2 (bumps to Node 18+) https://github.com/11ty/eleventy-utils/releases/tag/v2.0.0
• @11ty/recursive-copy from v3 to v4 (bumps to Node 18+, dependency cleanup) https://github.com/11ty/recursive-copy/releases/tag/v4.0.0
• entities from v5 to v6 (upstream change related to deep import paths https://github.com/fb55/entities/releases/tag/v6.0.0)

eleventy-benchmark Build Performance

---------------------------------------------------------
Eleventy Benchmark (Node v22.13.1, 2500 templates each)
---------------------------------------------------------
Eleventy 3.0.0                                        
---------------------------------------------------------
.liquid: ... 3 runs:          
* Median: 1.43 seconds
* Median per template: 572 µs

.njk: ... 3 runs:             
* Median: 2.03 seconds
* Median per template: 812 µs

.md: ... 3 runs:              
* Median: 1.79 seconds
* Median per template: 716 µs

---------------------------------------------------------
Eleventy 3.1.0-beta.1                                        
---------------------------------------------------------
.liquid: ... 3 runs:          
* Median: 1.3 seconds (-10%)
* Median per template: 520 µs (-10%)

.njk: ... 3 runs:             
* Median: 1.81 seconds (-11%)
* Median per template: 724 µs (-11%)

.md: ... 3 runs:              
* Median: 1.61 seconds (-11%)
* Median per template: 644 µs (-11%)

We’re showing the benchmark from the latest beta here — there were no core code changes between v3.1.0-beta.1 and v3.1.0.