tailwind.css not being created on the first run when the directory doesn't exist

[pupeno]

I'm not sure if this the right place to report this bug, I'm not even sure if this is a bug.

I have a Rails 7 project created recently with the --css=tailwind option. At some point apparently I deleted app/assets/builds/.keep which caused the directory app/assets/builds to just not be created git clone. The odd result was this: when deploying to heroku, when heroku would run rake asset:precompile, it would silently not create the tailwind.css file. But if I open a shell and run it again, it would create it.

I posted on Stack Overflow, so there are more details there: https://stackoverflow.com/questions/71538223/tailwind-css-not-being-generated-in-a-rails-7-project-in-heroku/71607506

I'm sorry about the low quality of this bug report, I don't understand all the moving pieces, just the symptoms. Maybe this will be obvious to someone that understand things a bit better. If there's a way for me to provide more and better info, please ask and I'll do my best.

[reefdog]

Perhaps my similar experience will help triangulate the issue: I just came aboard a Rails 7 project that uses this gem. I can setup and run the app, but rails test was throwing errors on ActionView::Template::Error: The asset "tailwind.css" is not present in the asset pipeline. Devs who had been on the project a while weren't getting that error.

Thanks to this issue, I first checked to ensure app/assets/build/ directory was present (it was), then looked for a app/assets/build/tailwind.css file inside (there was not), then ran rake assets:precompile manually to see if it generated the app/assets/build/tailwind.css file (it did). After which, the test ran cleanly.

So, like @pupeno, I'm unsure if the problem actually lies with this gem, or with Rails not actually precompiling assets properly, or what. But here are the symptoms in case they're useful!

[aluisioalves123]

Hello, I was having the same problem and when I was running rake assets:precompile it gave me this error message:

The problem was in the directory, the directory of my project was "Área de Trabalho" which means "Desktop" in portuguese (Im from Brazil).

So to solve the problem, I simply put my project folder in my root and then precompile it again.

Hope it helps

[flavorjones]

@aluisioalves123 You're experiencing a different problem -- a bug reported at #184 and fixed at #197.

[flavorjones]

@reefdog @pupeno Sorry you're experiencing problems. Although this gem hooks into the rake tasks test:prepare and db:test:prepare, you may still need to invoke assets:precompile or tailwindcss:build in your CI or deployment pipelines. Does that makes sense?

[stevepolitodesign]

I'm running into a similar issue, and want to reference rails/rails#47719 as a possible solution.