Tailwind without NodeJS

Hey @dealloc – Nice work! The phoenix team actually went to start on this very thing today. Any interest in transferring to the Phoenix org so we can own esbuild and tailwind packages without duplicating efforts?

hey @chrismccord of course! Had I known you guys were working on this I would’ve patiently waited
If you can give me some guidance on how to get that started I’m more than glad to transfer!

For the hex package:

$ mix hex.owner transfer tailwind chris@chrismccord.com

Then on GitHub, got to the settings page and near the bottom is the “Danger Zone”, and you can click transfer and transfer to the phoenixframework org.
https://github.com/dealloc/tailwind_cli/settings

Thanks for doing the leg work on this! I am beyond excited that we now have a dependency-free tailwind experience for phoenix users!

I transferred ownership for the hex package, but when I try to move the Github repository into phoenixframework I get the error “You don’t have permission to create public repositories on phoenixframework”
any workaround?

I was so excited when I came across the dependency free Tailwind CLI that I just had to integrate it, esbuild did it so effortlessly I couldn’t resist building something similar

Thanks so much! I’ll push the repo up on my side

How can I use Tailwind CSS IntelliSense - Visual Studio Marketplace when installing tailwind with this package?

I get this error from the plugin:

[Error - 11:10:05 AM] Tailwind CSS: Can't resolve 'tailwindcss' in '/<path-to-app>/assets'

So the plugin finds the generated tailwind.config.js but not tailwindcss.

When I install with

npm install -D tailwindcss

the plugin works.

You’ll need to copy the binary to somewhere in your $PATH if the vscode plugin requires it to be available globally

I copied _build/tailwind-linux-x64 to the path, also tried renaming to tailwindcss - still does not work. Also npm i -g tailwindcss does not work.

This is really very exciting! And kudos to the tailwind folks for accommodating to those of us who don’t care much for nodejs.

Thanks @dealloc and @chrismccord, I heard about this today and spent 15 mins updating my blog to remove NodeJS and the other dependencies.

It all worked a treat and I documented what I did here.

Thanks again guys.