3 ms·

Question for those developers who, like me, have no f/end build step: How would I use tailwind without a f/end build step? All the examples of using tailwind 4.

Question for those developers who, like me, have no f/end build step: How would I use tailwind without a f/end build step? All the examples of using tailwind 4.0 on the linked site assume a f/end build step. My project does not use (and I have no plans to include) npm, or PostCSS, etc.

rahkiin 2y ago
For a static site I have, I manually run the Tailwind tool when I include new classes. It generates style css and I commit this file to git.
- lelanthran 2y ago
  Thanks; I actually did not know there was one until you and the sibling poster told me. To anyone else with the same question: See https://tailwindcss.com/blog/standalone-cli https://tailwindcss.com/blog/standalone-cli
stevoski 2y ago
This is what keeps me from using Tailwind too. I simply do not want to add the maintenance headaches of an npm-based build process to my project.
- lelanthran 2y ago
  > I simply do not want to add the maintenance headaches of an npm-based build process to my project. Apparently I was just too blind to find it - here is how you can (presumably) use tailwind without pulling in npm and node.js. https://tailwindcss.com/blog/standalone-cli https://tailwindcss.com/blog/standalone-cli
- GrzegorzWidla 2y ago
  Vite dev, preview and build scripts make it so stupidly simple that I can’t believe people don’t pull it for all, including the simplest, sites. Plus I couldn’t imagine developing without TypeScript and hot reloads in 2025.
burgerrito 2y ago
I'm pretty sure the point of using TailwindCSS is to use build step. There is another way, it uses Tailwind's CDN. But I think even the developer don't recommend it outside of development phase If you don't want to use NPM, I can recommend Tailwind's standalone CLI
- lelanthran 2y ago
  > If you don't want to use NPM, I can recommend Tailwind's standalone CLI Didn't know there was one. Will look into it.

rahkiin 2y ago

For a static site I have, I manually run the Tailwind tool when I include new classes. It generates style css and I commit this file to git.

lelanthran 2y ago
Thanks; I actually did not know there was one until you and the sibling poster told me. To anyone else with the same question: See https://tailwindcss.com/blog/standalone-cli https://tailwindcss.com/blog/standalone-cli

stevoski 2y ago

This is what keeps me from using Tailwind too. I simply do not want to add the maintenance headaches of an npm-based build process to my project.

lelanthran 2y ago
> I simply do not want to add the maintenance headaches of an npm-based build process to my project. Apparently I was just too blind to find it - here is how you can (presumably) use tailwind without pulling in npm and node.js. https://tailwindcss.com/blog/standalone-cli https://tailwindcss.com/blog/standalone-cli
GrzegorzWidla 2y ago
Vite dev, preview and build scripts make it so stupidly simple that I can’t believe people don’t pull it for all, including the simplest, sites. Plus I couldn’t imagine developing without TypeScript and hot reloads in 2025.

burgerrito 2y ago

I'm pretty sure the point of using TailwindCSS is to use build step. There is another way, it uses Tailwind's CDN. But I think even the developer don't recommend it outside of development phase If you don't want to use NPM, I can recommend Tailwind's standalone CLI

lelanthran 2y ago
> If you don't want to use NPM, I can recommend Tailwind's standalone CLI Didn't know there was one. Will look into it.