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…
github.com/rdela/eleventeen/pu…
v9 patches by rdela · Pull Request #47 · rdela/eleventeen
partial v9 patches https://github.com/11ty/eleventy-base-blog/releases/tag/v9.0.0GitHub
This entry was edited (3 weeks ago)
Eleventy 🎈 v3.0.0
in reply to famebot • • •famebot
in reply to Eleventy 🎈 v3.0.0 • • •v9 patches by rdela · Pull Request #47 · rdela/eleventeen
GitHubfamebot
in reply to famebot • • •Eleventy 🎈 v3.0.0
in reply to famebot • • •github.com/11ty/eleventy-plugi…
github.com/11ty/eleventy-plugi…
Conditional tags · Issue #8 · 11ty/eleventy-plugin-bundle
GitHubfamebot
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
Ricky de Laveaga
in reply to famebot • • •famebot
in reply to Ricky de Laveaga • • •Bob Monsour
in reply to famebot • • •Eleventy 🎈 v3.0.0
in reply to Bob Monsour • • •famebot
in reply to Eleventy 🎈 v3.0.0 • • •