-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
[v4] FreeBSD: Cannot find module @tailwindcss/oxide-freebsd-x64/tailwindcss-oxide.freebsd-x64.node #15731
Comments
It looks like the binary is missing in the dependency, see https://www.npmjs.com/package/@tailwindcss/oxide-freebsd-x64?activeTab=code |
Had to switch to Debian and update my Dockerfile to get this working:
It looks like |
Same here! |
Hey! Closing this as as a duplicate of #15806. That other issue also has a downstream bug report rom npm that you might find interesting. |
I don't think it is correct to mark this as duplicate. #15806 is about the linux arm package not being installed automatically when it should, but being functional once installed. This issue is about the FreeBSD binary package not being functional even once actually installed, due to the actual binary file not being present in the package:
Maybe FreeBSD is not officially supported, but having an npm package claiming support, but missing the actual binary file looks a little strange. Is it planned for the package to be filled up at a later time? |
Oh, I see, sorry for that! Yep that is indeed not great. It seems we haven't wired up CI to build for freebsd yet. Lightningcss has an example of how this could be done though: https://github.com/parcel-bundler/lightningcss/blob/master/.github/workflows/release.yml#L163 We'll look into it, sorry! |
Thanks for looking into this! I hope Github won't be too long to add FreeBSD support in their Runner as more and more projects are switching to Github CI/CD and the lack of support becomes problematic (see also actions/runner#385).. |
Closes #15731 This PR adds a FreeBSD build target to our CI workflows. It was tested on CI: https://github.com/tailwindlabs/tailwindcss/actions/runs/13159185517/job/36723613079 However, due to the build not emitting final npm packages, we don't have a way to actually test the final package before we ship it to an insiders release. --------- Co-authored-by: Robin Malfait <malfait.robin@gmail.com>
Merged a PR to add the FreeBSD builds. If you could help us test that this works as expected, that would be great. You should be able to just use the latest npm i tailwindcss@insiders @tailwidncss/vite@insiders # etc... |
@philipp-spiess THaks for the quick fix! I just tested it in a very small vite project I had, it is a very very simple web page I keep around just in case, and I configured it to use vite and tailwind as an experiment. It works fine, generates correct css. I noticed the generated CSS is relatively big, it includes all color variables, which, I gather, I need to disable myself via css It also includes some other values I'm not using (for example what looks as a spinning animation). Is this expected? |
Replying to myself I notice the problem with unused variables is known and being worked on in #16211 Looking forward to that one landing! |
What version of Tailwind CSS are you using?
4.0.0
What build tool (or framework if it abstracts the build tool) are you using?
vue3
vite/6.0.11 freebsd-x64 node-v20.12.2
What version of Node.js are you using?
20.12.2
What browser are you using?
Firefox
What operating system are you using?
FreeBSD
Describe your issue
This is with:
Thanks!
The text was updated successfully, but these errors were encountered: