6.0.1 (Eleventy 3 … and more)

I'm a dope and forgot to test a couple of things; plus I updated to the latest Tailwind and bumped the version number in package.json.

Full Changelog: 6.0.0...6.0.1

Eleventy 3.0

Update Eleventy (3.0) and other dependencies

Eleventy 2.0.0 and Tailwind 3.2.7

Learn more about Eleventy 2.0.0 (and, how to upgrade it) as well as Tailwind 3.2.7.

Improve build speed

This small adjustment improves the build speed; see my low-effort test results here: #132 (comment)

Thanks to @lud, @ryanccn, and @geshan for their assistance on this one.

Build Tailwind _after_ Eleventy

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.

Set the default template engine to njk

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:

• sets njk as the default template engine, and
• changes {{ content }} to {{ content | safe }}, which is an njk feature

Minor bugfix and polish

{{ 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. 🤞

4.1.0

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);
};

4.0.0

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.

3.0.1

Minor polish, adjustments, etc. See the associated commit message for details.