Closed nate-sys closed 11 months ago
Got it to work by nuking my tailwind install and creating a new project. I don't know how to reproduce the issue, but I think it happens when the initial tailwind download fails when setting up a project. Maybe it tries to run the incomplete binary that didn't download correctly? Though, this doesn't explain why the pages just stopped being styled during my first run, where everything downloaded correctly. Curious.
Interesting, I'll investigate this soon.
I was able to reproduce the first error by running bb css
on a new project and then hitting ctrl-c
while the tailwind download was in progress, then doing chmod +x bin/tailwindcss
. I added some code that will detect if the binary is corrupted and print an error message suggesting that you delete it if so (which will cause the binary to be redownloaded the next time you run the original command). That's on master already (see https://forum.tfos.co/t/biff-v0-7-13/81), and I'll publish a release on github soon.
As for how your tailwind binary got in that state after it was already working, I have no idea... but if it ever resurfaces, rm bin/tailwindcss
should do the trick.
The Cannot find module '@tailwindcss/forms'
error is there because the default tailwind.config.js
file specifies a dependency on the @tailwindcss/forms
plugin, which is bundled with the binary. If you've installed tailwindcss locally or globally with npm, you'll need to also install @tailwindcss/forms
with npm.
The issue
After following the getting started guide, the css suddenly stopped working. None of the pages were being styled and trying to run
bb css
manually errors withError while executing task: css
.I tried to run it again after installing tailwindcss globally using npm and got this error:
Creating a new project, and running
bb dev
again leads to this error:System information
OS: Void Linux Processor: x86_64 Babashka :
1.3.182
Npm:9.5.1