Running tailwind:build fails silently if .env files are present

[trobin91]

Hello everyone,

I am stuck on a really weird bug, which might be more linked to the tailwind binary itself.

Since updating to tailwind 4.x.x, I have noticed that running php bin/console tailwind:build fails:

php bin/console tailwind:build -v

 ! [NOTE] Executing Tailwind (pass -v to see more details).                                                             

  Command:
    '/app/var/tailwind/v4.1.12/tailwindcss-linux-x64-musl' '-i' '/app/assets/styles/app.css' '-o' '/app/var/tailwind/app.built.css'

                                                                                                                        
 [ERROR] Tailwind CSS build failed: see output above.       

Even running /app/var/tailwind/v4.1.12/tailwindcss-linux-x64-musl' -h returns 1 without output.

I discovered that the issue came from the presence of a .env or .env.local in the working directory when launching the command.
Running -/tailwind/v4.1.12/tailwindcss-linux-x64-musl' -h in /app/var works, or renaming/moving the .env or .env.local files also work,

Even a clean .env file on a new Symphony project makes it crash.

My setup is php-8.4 on a nginx:alpine base docker image.

Thank you for your help,
Thibault

[bocharsky-bw]

Hey @trobin91 ,

Could you try running that via symfony console tailwind:build -vvv? Please, notice using symfony console command instead of bin/console, and also -vvv to set verbose output level to max. The same error?

If you have troubles with env files presented, I would say that some code in your app is exeucuting but fails due to wrong env vars set up (or missing the correct env var value). If so, then most probably we should see some errors in the Symfony logs, so please double check the logs for any breadcrumbs of this error.

Also, you can try to comment out everything in your Tailwind CSS files and try to run the tailwind:build command on the empty CSS file, is it still an error? If no error, try to write some simple CSS and rerun again, then continue uncommenting more code to find the problem spot.

That's all I can think about for now