Closed bastien70 closed 1 year ago
Hi!
Hmm, these issues might be unrelated - both look very strange. I wonder, in both cases, what happens if you run the commands manually/directly on the command line? For example:
/home/bastien/Documents/Symfony/test_tailwind_bundle/var/tailwind/tailwindcss-linux-x64 -i '/assets/styles/app.css' -o '/var/tailwind/tailwind.built.css' --watch
(run it both with and without the --watch
). Are files created? Same error with watch or not? The --watch
error is especially odd since you are using a new project, so there should be very few files being watched (the config watches assets/*
and templates/*
by default, as defined in the tailwind.config.js
file).
Hello!
Uh, listen, I just tried the same commands again today, without having changed anything, and there, everything is going wonderfully well. I don't know what changed.
Sorry for the wasted time
Hey! Thanks for this bundle!
I just want to try it, so I did :
Juste before the last command I check the base.html.twig, it's okay there is the following lines :
And in the
assets/styles/app.css
, I've this :But when running the last command,I've this error :
Seems that this error only pop when launching
php bin/console tailwind:build --watch -v
. When launchingphp bin/console tailwind:build
, I've this :Buuuut, there is no file created. According the logs, it sgould create a
tailwind.built.css
file invar/tailwind
, but there is no fileThank you! :D