-
Notifications
You must be signed in to change notification settings - Fork 185
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
new rails application stalls at tailwind install/build #509
Comments
Hi @blairanderson, and what happens if you run this command?
If the problem persists, i'd tend to think it's a problem with the tailwindcss-cli executable rather than this gem. Similar issues have been reported in the past (see #499, though I don't think it's exactly your problem). Btw, I tried your command and worked without issues (though on a docker container). |
I'm experiencing the same issue after installing it in an existing Rails project. The process gets stuck at:
I tried running the command you suggested, but it didn’t work. Do you have any other recommendations? |
Hi @brandongs-MP, Unfortunately, your output is not enough for me to tell what might be wrong. If you're running the standalone cli tool by tailwind (the output of running Please refer to this comment. How are you running this command? Are you running on docker? mac? The more info you can share, the better! |
I'm facing the same issue as well. I'm running my project on an Apple Silicon M3 Max computer. What exactly is Bun? Why is Tailwind using it? |
For anyone having trouble, could you try running https://github.com/rails/tailwindcss-rails/releases/tag/v3.3.1 instead? Tailwind recently moved a big version. Maybe related to that? |
I had to specify that version. |
This didn't work. It stalled |
@dhh @patriciomacadden yes this worked. Gemfile $ rails tailwindcss:build
Rebuilding...
Done in 468ms. |
Tailwind v4's CLI executable is built using Bun (by this, I mean the upstream tailwindlabs/tailwindcss project). @iCueto @blairanderson If v3 is working for you, then this is most likely an issue with the upstream tailwind CLI executable that is being packaged by the If someone who can reproduce this issue would be kind enough to report their experience upstream on the tailwindlabs/tailwindcss project, I'd be very grateful. In the meantime, you may want to stay on |
FWIW I also receive a hanging tailwindcss:build on an existing Rails 8.0.2 app. I did I was on tailwindcss-rails 4.2.0, tailwindcss-ruby 4.0.12 and was updated to 4.0.16 and 4.2.1. So something in between there blew it up. |
If someone who can reproduce this issue would be kind enough to report their experience upstream on the tailwindlabs/tailwindcss project, I'd be very grateful. In the meantime, you may want to stay on tailwindcss-rails v3.3.1, which pins to Tailwind v3. |
Sorry Mike, I forgot to include a "I will go over to the tailwindlabs/tailwindcss project" (was +1 ing it since I think I have a different version, in case that was helpful!) |
@flavorjones I have a similar issue with the latest |
@octave Thanks for sharing your experience. I'll say it again, though: please report your experience upstream. The only difference between those two versions of tailwindcss-ruby is the executable being packaged, both of which came from the upstream releases. |
FWIW in tailwindlabs/tailwindcss#17379 a regex backtracking issue has been identified that's causing hangs for some people. I'm not positive, but I'm hopeful, that this addresses some of what folks are reporting here. |
I've packaged up Release v4.0.17 · flavorjones/tailwindcss-ruby, please give it a go and see if it addresses your issue! |
Verified fixed on my end!!! Thank you for the quickness! 🥇 |
@flavorjones Still having the issue on Rails 8.0.2 after upgrading to 4.0.17 Dev enviroment: MacBook Pro - Apple M1 (2020) - 15.3.2 (24D81) Gemfile
% cat Gemfile.lock | grep tailwindcss
% bin/rails tailwindcss:build
bun -v I have bun 1.2.6 but tailwindcss:build uses 1.2.4. Maybe related? |
@leoplct Sorry you're still having issues. If you are seeing some sort of Bun error message, then you should report that upstream to tailwindlabs/tailwindcss, along with your hardware information. Bun is what's used by tailwindlabs/tailwindcss to build the binary executable CLI, which is what is packaged up by tailwindcss-ruby and used by this gem. If there's a hardware issue then they need to know about it in order to address it, and opening an issue may get their attention. |
I solved by downgrading and installing again Downgrading
Installing again
Upgrading
|
@flavorjones that's it! Works for me too! Thank you for being always so fast! |
Hi @flavorjones, same as @leoplct I'm having the issue on a Macbook M1 OS Ventura with a fresh install of Rails 8.0.2. bundle exec which tailwindcss
> /Users/user/.asdf/installs/ruby/3.3.6/bin/tailwindcss
bundle exec tailwindcss --help
> ["/Users/user/.asdf/installs/ruby/3.3.6/lib/ruby/gems/3.3.0/gems/tailwindcss-ruby-4.0.17-x86_64-darwin/exe/x86_64-darwin/tailwindcss", "--help"]
> hanging forever |
@niconisoria Please see my response above and report it upstream. |
sits there forever.
control+c to break:
running install again gets to build step and freezes:
running VERBOSE doesn't do much:
The text was updated successfully, but these errors were encountered: