Eleventy 🎈 v3.1.0-beta.1📮 New on the blog:
Calling all courageous canary testers for Eleventy v3.0
…in which we discuss the new v3.0.0-alpha releases!
James Doc@eleventy Just worked my way through the update; had a minor issue with layouts. Previously I had been using `{{ layoutContent | safe }}`, that appears to be broken now and requires `{{ content | safe }}`. Which looking at the documentation, might have been a change a while ago?
Related PR:
https://github.com/jamesdoc/jamesdoc.com/pull/33/files
@jamesdoc I don’t think `layoutContent` was _ever_ on the docs—where did you see it? It was an old 0.x feature that did get removed in 3.0.
(yes, `content` is the recommended name moving forward)
Bob Monsour@eleventy The 11tybundle.dev site is now running 3.0 canary. Read all about it… https://11tybundle.dev/blog/11ty-bundle-24/
Dan Ryan 
(he/she/they)@eleventy I've tried it on dryan.com, works as expected after following the migration guide!
@d Thanks Dan!
Saneef H. Ansari@eleventy Went full on ESM with v3.0-alpha on https://saneef.com. No sweat!
Kevin Yank@eleventy Upgraded https://kevinyank.com easily! Sticking with CJS made it trivial to the point of boredom (in the best way)!
@eleventy …so went for the ambitious switch to ESM. It’s working perfectly with only one minor issue I had to overcome:
The JSDoc type annotation for eleventyConfig broke. Issue reported with my current work-around: https://github.com/11ty/eleventy/issues/3127
Documentation for UserConfig type definitions doesn't work in ESM · Issue #3127 · 11ty/eleventy
Operating system macOS Sonoma 14.2 Eleventy 3.0.0-alpha.2 Describe the bug The 11ty docs recommend this as the way to get TypeScript-powered autocomplete on the eleventyConfig object: /** @param {i...
@sentience thank you for filing an issue!
reverentgeek@eleventy I got 3.0.0-alpha.4 running on my blog. I decided to change my default project type to module and rename my .js files to .cjs. I may have missed something in the post, but it wouldn't build. I had to rename .eleventy.cjs back to .js and upgrade that one file to module syntax. All the others worked with the .cjs extension.
@reverentgeek does your config file have `require("@11ty/eleventy")` in it anywhere?
@eleventy No, it doesn't. Should it?
@reverentgeek No, just asking the obvious questions first! Can you supply your CommonJS config that was failing?
Konrad S.@eleventy Stupid sexy piece of lib 😅 Have to look into the upcoming features now!