Skip to main content


in case @eleventy and/or anyone in #11ty world has a sec, what is the easiest way to convince v3.0+ bundler not to optimize out a bit of client JS in the layout? 3.0.0-beta.1 worked fine so must’ve changed between then and v3 release.
github.com/rdela/eleventeen/pu…
This entry was edited (3 weeks ago)
in reply to Eleventy 🎈 v3.0.0

still not sure what (if anything), to file, beyond reporting back about the armchair review suggestion I will try. I added what I gathered here, not sure if you saw github.com/rdela/eleventeen/pu…
in reply to famebot

that JS only runs client side, so my assumption was between beta 1 and release you added some fancy performance features to bundling that detected untouched codepaths
in reply to famebot

ah, my hunch is that it’s this:
github.com/11ty/eleventy-plugi…
github.com/11ty/eleventy-plugi…
This entry was edited (3 weeks ago)
in reply to Eleventy 🎈 v3.0.0

yep that “prunes empty script/style/link bundles” seems likely 🌸

Unbundling JS still seems like the obvious solution to this, will give it a whirl

in reply to Ricky de Laveaga

@rdela @bobmonsour I let this sit for so long already I think I will archive this repo if there isn’t an easy solution since I am not using it anymore.
in reply to Bob Monsour

@bobmonsour @rdela my armchair review of the issue: Eleventy only “optimizes” JS code nested inside of `{% js %}` shortcodes (in the base blog configuration). If you want to remove this feature, just delete the `eleventyConfig.addBundle("js")` line from the config file!