It‘s (j)ust (e)leventy and (t)ailwind … OK, and a few other things; it‘s still *really* small though.
Learn more about Eleventy 2.0.0 (and, how to upgrade it) as well as Tailwind 3.2.7.
This small adjustment improves the build speed; see my low-effort test results here: https://github.com/marcamos/jet/issues/132#issuecomment-1312276910
Thanks to @lud, @ryanccn, and @geshan for their assistance on this one.
Uses
eleventy.after
event to build tailwind after HTML is ready.
Thank you so much, @geshan!
P.S. This also bumps a dependency or two.
This is a (late) amendment to 4.1.1; I realize, now, that the safe
filter is a Nunjucks (njk) feature. As njk is my preferred template engine and I use it on every site I base off of jet, I figured I'd set it as the default.
So, this release:
{{ content }}
to {{ content | safe }}
, which is an njk feature{{ content | safe }}
has been updated to {{ content }}
in base.html. Eleventy (or, perhaps Nunjucks?) threw an error and I couldn't find anything online explaining why, so removing it seemed like the next best option. 🤞
Upgrade to Eleventy v1!
You can use the helper plugin @11ty/eleventy-upgrade-help
to help you upgrade:
npm install @11ty/eleventy-upgrade-help
// .eleventy.js
const UpgradeHelper = require("@11ty/eleventy-upgrade-help");
module.exports = function(eleventyConfig) {
eleventyConfig.addPlugin(UpgradeHelper);
};
If you want to upgrade your project from Tailwind CSS v2.x to v3.x, the Tailwind folks have a wonderful Upgrade Guide you should review.
Minor polish, adjustments, etc. See the associated commit message for details.
tailwind.css
file now auto-reloads the browser (thanks so much @timkley!)package.json
scripts have been updated to use Tailwind's CLI, negating the use of postcss and its own dependencies (thanks so much @timkley!)