You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a project running Next.js that is using tailwindcss v4 which includes lightningcss. When attempting to run my app, I'm given the following error:
In my node modules, I'm seeing both expected packages for my system (arm64 macbook): lightningcss, and lightningcss-darwin-arm64. However, the error shows that on import, lightning attempted to load in lightningcss-darwin-x64 instead.
As a sanity check, I tried running the next js app with and without turbopack but that didn't change the error. I also tried bun -e "console.log(process.arch)" and as expected, it returned arm64.
Beyond this, I'm not really sure what to try and will likely be reverting to tailwindcss v3 until I have more time to investigate the issue further. However, let me know if there are any more details that would be helpful and I'll happily provide!
The text was updated successfully, but these errors were encountered:
Issue synopsis
I have a project running Next.js that is using tailwindcss v4 which includes lightningcss. When attempting to run my app, I'm given the following error:
In my node modules, I'm seeing both expected packages for my system (arm64 macbook):
lightningcss
, andlightningcss-darwin-arm64
. However, the error shows that on import, lightning attempted to load inlightningcss-darwin-x64
instead.Investigation so far
A cursory check led me to this file where it seems that
process.arch
is somehow being set tox64
. I'm not really sure how that's possible but that is indeed what is happening.As a sanity check, I tried running the next js app with and without turbopack but that didn't change the error. I also tried
bun -e "console.log(process.arch)"
and as expected, it returnedarm64
.Beyond this, I'm not really sure what to try and will likely be reverting to tailwindcss v3 until I have more time to investigate the issue further. However, let me know if there are any more details that would be helpful and I'll happily provide!
The text was updated successfully, but these errors were encountered: