tailwind.css not being created on the first run when the directory doesn't exist #158
Comments
|
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 Thanks to this issue, I first checked to ensure 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! |
|
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 |
|
@aluisioalves123 You're experiencing a different problem -- a bug reported at #184 and fixed at #197. |
|
I'm running into a similar issue, and want to reference rails/rails#47719 as a possible solution. |
There appears to be a [bug][1] with tailwindcss-rails, or possibly Rails, that is affecting how assets are precompiled on a cloned repository. Prior to this commit, we would get the following error after cloning the repo and running the test suite: ```text ActionView::Template::Error: The asset 'tailwind.css' was not found in the load path. ``` One solution is to run `test:prepare` in the setup script which will generate the assets. There is an [open pull request][2] against Rails that would introduce this change based on [similar feedback][3] [1]: rails/tailwindcss-rails#158 [2]: rails/rails#47719 [3]: rails/rails#47210 (comment)
There appears to be a [bug][1] with tailwindcss-rails, or possibly Rails, that is affecting how assets are precompiled on a cloned repository. Prior to this commit, we would get the following error after cloning the repo and running the test suite: ```text ActionView::Template::Error: The asset 'tailwind.css' was not found in the load path. ``` One solution is to run `test:prepare` in the setup script which will generate the assets. There is an [open pull request][2] against Rails that would introduce this change based on [similar feedback][3] [1]: rails/tailwindcss-rails#158 [2]: rails/rails#47719 [3]: rails/rails#47210 (comment)
There appears to be a [bug][1] with tailwindcss-rails, or possibly Rails, that is affecting how assets are precompiled on a cloned repository. Prior to this commit, we would get the following error after cloning the repo and running the test suite: ```text ActionView::Template::Error: The asset 'tailwind.css' was not found in the load path. ``` One solution is to run `test:prepare` in the setup script which will generate the assets. There is an [open pull request][2] against Rails that would introduce this change based on [similar feedback][3] [1]: rails/tailwindcss-rails#158 [2]: rails/rails#47719 [3]: rails/rails#47210 (comment)
There appears to be a [bug][1] with tailwindcss-rails, or possibly Rails, that is affecting how assets are precompiled on a cloned repository. Prior to this commit, we would get the following error after cloning the repo and running the test suite: ```text ActionView::Template::Error: The asset 'tailwind.css' was not found in the load path. ``` One solution is to run `test:prepare` in the setup script which will generate the assets. There is an [open pull request][2] against Rails that would introduce this change based on [similar feedback][3] [1]: rails/tailwindcss-rails#158 [2]: rails/rails#47719 [3]: rails/rails#47210 (comment)
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=tailwindoption. At some point apparently I deletedapp/assets/builds/.keepwhich caused the directoryapp/assets/buildsto just not be created git clone. The odd result was this: when deploying to heroku, when heroku would runrake asset:precompile, it would silently not create thetailwind.cssfile. 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.
The text was updated successfully, but these errors were encountered: