👋 Great project! about jet

One thing I don't get is, why is postcss and tailwind both involved in the build process?

In the build process:

$ npm run tailwind && postcss src/css/styles.css --replace

Isn't Tailwind run twice?

[marcamos]

Hello Ryan!

Thanks for the kind words.

To (try) to answer your question: I built jet before Tailwind included its new purge option, so it was setup to purge and minify 'manually'.

A bit later, when Tailwind released its built-in purge option, I gave it a try. I compared the size of its output CSS to the size of my 'manual' solution's output CSS, and found the new purge option's output CSS to be larger. Bummer.

I didn't really investigate why, but quickly decided that I would just stick with my original 'manual' process, simply because its output was smaller.

Does that help?

Oh I see

But

$ npm run tailwind && postcss src/css/styles.css --replace

Tailwind is included in PostCSS, so the Tailwind build process is run on an already built Tailwind file...

const plugins = [
  tailwindcss('tailwind.config.js'),
  purgecss({
    content: ['src/**/*.html']
  }),
  cssnano()
]

[marcamos]

Aha, I understand what you mean now — thanks for the clarification! You may be right; I'm going to do some testing as soon as I can, and I'll update this issue.

[marcamos]

I did some testing and here's what I discovered:

When I adjust the build script to be the following: "postcss src/css/styles.css --replace && npm run clean && npx @11ty/eleventy", the compiled CSS no longer picks up the classes in the HTML.

[marcamos]

Aha, but if I do the opposite: remove the call to Tailwind from the postcss.config.js file, as seen in 339f02a, it continues to work as desired.

Thank you so much @ryanccn! This has been a great tip.

Glad to help! 😇