I’ve seen weird issues like that for people running macOS on Apple Silicon when Tailwind runs under Rosetta emulation, could that apply to you?
steffend
Phoenix Core Team
Kevo
steffend
Phoenix Core Team
@Kevo I think it’s related to Use bun-baseline for all x64 builds by philipp-spiess · Pull Request #17267 · tailwindlabs/tailwindcss · GitHub - can you please bump the Tailwind version in your config.exs to a version >= 4.0.15 and see if that fixes it? We already bumped Tailwind to 4.1.7 a couple of weeks ago, but that change will only be in the next release candidate (which should be released this week!).
Kevo
I bumped it to 4.1.7 and ran mix setup. It downloaded v4.1.7 and then again gave the error.
** (Mix) mix tailwind hello exited with 132
steffend
Phoenix Core Team
Unfortunate 
Can you please try to reproduce this with the standalone binary directly? You can download the tailwindcss-macos-x64 binary from Releases · tailwindlabs/tailwindcss · GitHub and then report an issue in the TailwindCSS repo if it also doesn’t work. (Note that you may need to run xattr -d com.apple.quarantine /path/to/tailwindcss-macos-x64 when downloading the file in a browser).
Kevo
It doesn’t work. From what I read in the tailwind bug reports they use something called bun to compile .js and looking at reports on the bun repo I get the impression that they have just decided to not bother with older cpus that don’t have AVX2. It seems to affect linux users as well who are running older CPUs. I’m not sure how compelling AVX2 is for this use case, but it’s definitely unfortunate for those of us that have perfectly functional and usable machines that we may be left behind by CSS of all things for lack of a fancy SIMD block. I guess I will have to stick with the old version unless someone who knows a lot more about tailwind and bun than me can come up with a workaround of some sort.
steffend
Phoenix Core Team
Yeah, Tailwind v4 also decided to require quite recent browser versions, which is also unfortunate from a user perspective. In my opinion there’s nothing wrong with sticking with Tailwind v3 - we just cannot maintain support for both versions in the generators, that’s why we use the newer version there.
Kevo
I found this issue in Bun that maybe gets to the root of the problem, but I am barely literate in phoenix and elixir at this point and have no understanding of tailwind or bun. Is it possible that a fix on this bun issue would result in the tailwind tooling eventually working for me in phoenix? Or is this a situation where the software would need to be built specifically for the older CPUs meaning I would have to build the software myself on my machine in order to get it to work properly?
steffend
Phoenix Core Team
I don’t know any details about Bun internals either, but Tailwind should already set Bun to “baseline”, which should generate code that works without AVX2. I’d recommend to just open up an issue in the Tailwind repo, since they should know best if it is supposed to work or not based on their usage of Bun.
Kevo
I opened an issue. Hopefully this turns out to be a simple fix somewhere. I can run the linux-x64 version in a VM on my machine so I don’t think there is any reason the Mac version shouldn’t be able to run as well. Maybe it’s just some compiler setup somewhere that needs to be tweaked. 