tailwindcss: Can't build on Linux ARM -> cannot find module '@tailwindcss/oxide-linux-arm64-gnu'

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?

Vite 6

What version of Node.js are you using?

22.12.0

What browser are you using?

Occurs in CLI

What operating system are you using?

Ubuntu Linux on arm64

Reproduction URL

/

Describe your issue

When running tsc && vite build the build fails and gives the following error:

error during build:
[vite:css] Failed to load PostCSS config (searchPath: [...]): [Error] Loading PostCSS Plugin failed: Cannot find module '@tailwindcss/oxide-linux-arm64-gnu'

About this issue

  • Original URL
  • State: closed
  • Created 2 years ago
  • Reactions: 38
  • Comments: 64 (7 by maintainers)

Commits related to this issue

Most upvoted comments

Saw these errors come up on vercel builds.

Added this to my package.json:

  "optionalDependencies": {
    "@tailwindcss/oxide-linux-x64-gnu": "^4.0.1",
    "lightningcss-linux-x64-gnu": "^1.29.1"
  }

And things worked again.

Edit: I realize that my architecture may be different than OP’s, but the technique might be helpful all the same – just replace the package names appropriately.

I experienced the same issue building inside an amd64 docker container. I had to manually pnpm add the @tailwindcss/oxide-linux-x64-gnu and lightningcss-linux-x64-gnu packages to run successfully.

I really doubt that it’s the intention that these packages should have to be manually installed

Agreed

Same issue here, but for macOS locally:

An error occurred in `next/font`.

Error: Cannot find module '@tailwindcss/oxide-darwin-arm64'

The optionalDependencies doesn’t work for me, at least not using pnpm and turborepo. And I dislike this method to specify manually these binaries, because every developer that works in the project that owns a different OS will be forced to do this.

The best would be a postscript coming from tailwind to decide based on the operating system which binary should be installed, but not as an explicit dependency in package.json.

  "optionalDependencies": {
    "@tailwindcss/oxide-linux-x64-gnu": "^4.0.1",
    "lightningcss-linux-x64-gnu": "^1.29.1"
  }

this did a trick for me

Also seeing this, but on amd64, had to manually add this to my Dockerfile:

npm i lightningcss-linux-x64-gnu @tailwindcss/oxide-linux-x64-gnu sass-embedded-linux-x64

I’m still continuing to get some odd deprecation warnings…

frontend-1  | Deprecation Warning on line 44, column 8 of file:///home/node/src/styles/globals.scss:44:8:
frontend-1  | Sass @import rules are deprecated and will be removed in Dart Sass 3.0.0.
frontend-1  |
frontend-1  | More info and automated migrator: https://sass-lang.com/d/import
frontend-1  |
frontend-1  | 44 | @import "tailwindcss";
frontend-1  |
frontend-1  | src/styles/globals.scss 45:9  root stylesheet

For this, you’d could consider replacing the @import like so:

-@import "tailwindcss";
+@import "tailwindcss/index.css";

The .css ending ensures Sass leaves the @import as-is and ensures Tailwind handles it properly.

Now using Node v22.15.0 (npm v11.3.0).

Upgraded to Tailwind CSS v4.1.6 — I can confirm the @tailwindcss/oxide error is gone. However, I’m still seeing the lightningcss error. Upgrading npm did not resolve this one.

RUN npm install <MODULE_FROM_LOG_THAT_COULD_NOT_BE_FOUND> <---- New Step

DUDE I can’t thank you enough!!

I ran npm install lightningcss-linux-x64-gnu. while in terminal and saw no difference; stopped and started the docker instance and it was WORKING. THANK YOU SO MUCH.

Going to attempt a build with the dockerfile from scratch.

Next up: getting it up on docker hub so I can get it up on a server.

THANK YOU SO MUCH.

Avoid tailwind 4.0.5

      "tailwindcss": "4.0.4",
      "@tailwindcss/node": "4.0.4",
      "@tailwindcss/postcss": "4.0.4",

clear node_modules and package-lock, npm i, yada yada

I’m receiving a similar error:

frontend-1  | Error: Cannot find module '@tailwindcss/oxide-linux-arm64-musl'

I’m using the Next.js framework on M3 (arm64) MacOS. I’m not sure if @Kaishiyoku is building from within a Docker container? I’m building inside an Alpine Linux Docker container, so I suspect that the difference in our error message is just Alpine busybox tooling (musl build libraries) vs Ubuntu’s (gnu) tooling.

Is it possible that Tailwind hasn’t setup something for arm64?

frontend-1  | (node:50) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
frontend-1  | (Use `node --trace-deprecation ...` to show where the warning was created)
frontend-1  | node:internal/process/promises:394
frontend-1  |     triggerUncaughtException(err, true /* fromPromise */);
frontend-1  |     ^
frontend-1  |
frontend-1  | Error: Cannot find module '@tailwindcss/oxide-linux-arm64-musl'
frontend-1  | Require stack:
frontend-1  | - /home/node/node_modules/@tailwindcss/oxide/index.js
frontend-1  | - /home/node/node_modules/@tailwindcss/postcss/dist/index.js
frontend-1  | - /home/node/node_modules/next/dist/build/webpack/config/blocks/css/plugins.js
frontend-1  | - /home/node/node_modules/next/dist/build/webpack/config/blocks/css/index.js
frontend-1  | - /home/node/node_modules/next/dist/build/webpack/config/index.js
frontend-1  | - /home/node/node_modules/next/dist/build/webpack-config.js
frontend-1  | - /home/node/node_modules/next/dist/build/webpack-build/impl.js
frontend-1  | - /home/node/node_modules/next/dist/compiled/jest-worker/processChild.js
frontend-1  |     at Function.<anonymous> (node:internal/modules/cjs/loader:1244:15)
frontend-1  |     at /home/node/node_modules/next/dist/server/require-hook.js:55:36
frontend-1  |     at Function._load (node:internal/modules/cjs/loader:1070:27)
frontend-1  |     at TracingChannel.traceSync (node:diagnostics_channel:322:14)
frontend-1  |     at wrapModuleLoad (node:internal/modules/cjs/loader:217:24)
frontend-1  |     at Module.<anonymous> (node:internal/modules/cjs/loader:1335:12)
frontend-1  |     at mod.require (/home/node/node_modules/next/dist/server/require-hook.js:65:28)
frontend-1  |     at require (node:internal/modules/helpers:136:16)
frontend-1  |     at Object.<anonymous> (/home/node/node_modules/@tailwindcss/oxide/index.js:206:31)
frontend-1  |     at Module._compile (node:internal/modules/cjs/loader:1562:14) {
frontend-1  |   code: 'MODULE_NOT_FOUND',
frontend-1  |   requireStack: [
frontend-1  |     '/home/node/node_modules/@tailwindcss/oxide/index.js',
frontend-1  |     '/home/node/node_modules/@tailwindcss/postcss/dist/index.js',
frontend-1  |     '/home/node/node_modules/next/dist/build/webpack/config/blocks/css/plugins.js',
frontend-1  |     '/home/node/node_modules/next/dist/build/webpack/config/blocks/css/index.js',
frontend-1  |     '/home/node/node_modules/next/dist/build/webpack/config/index.js',
frontend-1  |     '/home/node/node_modules/next/dist/build/webpack-config.js',
frontend-1  |     '/home/node/node_modules/next/dist/build/webpack-build/impl.js',
frontend-1  |     '/home/node/node_modules/next/dist/compiled/jest-worker/processChild.js'
frontend-1  |   ]
frontend-1  | }
frontend-1  |
frontend-1  | Node.js v22.13.1
frontend-1  | Static worker exited with code: 1 and signal: null
  • Next 15.1.6
  • Alpine 3.21.2
  • Node 22.13.1 (also tried Node 20 w/o success)
  • Tailwind 4.0

Just a note here: We added the postinstall script only to the oxide dependency. It can be that the other native extensions (lightningcss, @parcel/watcher) also experience these issues. If you run into issues with this package I recommend the same workarounds as before:

  1. Try to fix your lockfile so that the optional dependencies are properly resolving to the platform-specific ones
  2. Upgrade npm to the latest version for a fix for this issue.
  3. If nothing else helps, add the missing files as a manual dependency to your project to force them to be installed. Note that you shouldn’t have to add @tailwindcss/oxide-* related packages for this anymore.

Folks are referencing an issue in npm/cli being a cause for npm users. It seems like a PR was merged, but the team just cut a release a few days ago, so I’d expect about a month before another release is cut

See PR https://github.com/npm/cli/pull/8184

Manually installing lightningcss-linux-x64-gnu, and @tailwindcss/oxide-linux-x64-gnu in my yaml CI/CD setup file works as a temporary fix.

But TW should be able to identify the proper module it needs without manual intervention. Looking forward to an update.

I am developing on Apple M3 Max (arch=arm64, platform=darwin) and therefore this is also the place where I run my npm install package-xyz commands, which generate my package-lock.json file. After the development I move over to a CI/CD pipeline based on a node:22-bookworm image, which turns out to be platform=linux and arch=x64. I was able to solve the problem without downgrading.

My versions: next.js 15 react 19 tailwindcss 4.0.14 @tailwindcss/postcss 4.0.14

I am using npm ci (so only considering package-lock.json) to install the dependencies in the docker container and I was running in exactly the same problems.

My resolution worked like this

If you are using npm 8.19.0 or higher.

Reinstall @tailwindcss/postcss on your development using: npm install --platform=linux --arch=x64 @tailwindcss/postcss

It is possible that you need to ensure that the package-lock.json is been correctly updated, worst case by deleting package-lock.json and node_modules and reinstalling via npm install. After that the package-lock.json contains in addition to arm64 dependencies also the x64 linux dependencies see screenshot.

Image

Change to your platform and arch if you need something different, this should add both optional dependencies for your local environment in my case arch=arm64, platform=darwin and the docker environment linux x64. After that my build are running smooth again.


If you are not using npm 8.19.0 or higher

Try running the install process instead of using

npm ci with npm install

Ensuring that all optional dependencies are actually matching your target os and and arch. This is not recommended because depending on how you have defined your version it can lead to sideeffects and “auto-upgrades”.


Other option add an additional install command after your installation like

npm ci
# Extract installed version
INSTALLED_VERSION=$(npm list @tailwindcss/postcss --depth=0 | grep '@tailwindcss/postcss'  | awk -F@ '{print $3}')
npm i @tailwindcss/postcs@$INSTALLED_VERSION
npm run build

Same “trick” can be applied for other binary packages two, e.g. turbo …

I’m still encountering this issue when running in a container.

Version: "tailwindcss": "4.0.13"

Error:

Error: An error occurred in `next/font`.

Error: Cannot find module '@tailwindcss/oxide-linux-arm64-musl'

The optional dependency doesn’t work for me either.

I also have the same issue, and it’s not good at all… Removing node_modules and package-lock.json and then running npm i helps very partially (optionalDependencies don’t help) : The issue is that our team all have laptops with different CPUs and OS, and for Jenkins we have even another system. So to make it work, everyone should remove their node_modules and package-lock, and reinstall tailwindcss modules only specific for their systems. And none of them can be used on CI/CD. But using npm i without package-lock.json instead of a regular npm ci on CI/CD is dangerous due to possible fetching of untested versions of libs, and leads to unpredictable bugs on the production. So, currently there’s no a clean way to deploy it safely.

I’m also seeing this issue with pnpm, so it’s not just a npm issue.

Next.JS 15.1.6 TailwindCSS 4.0.4 NodeJS v22 Docker image is running Alpine Linux Running Docker on a M1 Mac

Error

#20 340.9 Error: Cannot find module '@tailwindcss/oxide-linux-arm64-musl'
#20 340.9 Require stack:
#20 340.9 - /app/node_modules/.pnpm/@tailwindcss+oxide@4.0.4/node_modules/@tailwindcss/oxide/index.js
#20 340.9 - /app/node_modules/.pnpm/@tailwindcss+postcss@4.0.4/node_modules/@tailwindcss/postcss/dist/index.js
#20 340.9 - /app/node_modules/.pnpm/next@15.1.6_@babel+core@7.26.7_react-dom@18.3.1_react@18.3.1__react@18.3.1/node_modules/next/dist/build/webpack/config/blocks/css/plugins.js
#20 340.9 - /app/node_modules/.pnpm/next@15.1.6_@babel+core@7.26.7_react-dom@18.3.1_react@18.3.1__react@18.3.1/node_modules/next/dist/build/webpack/config/blocks/css/index.js
#20 340.9 - /app/node_modules/.pnpm/next@15.1.6_@babel+core@7.26.7_react-dom@18.3.1_react@18.3.1__react@18.3.1/node_modules/next/dist/build/webpack/config/index.js
#20 340.9 - /app/node_modules/.pnpm/next@15.1.6_@babel+core@7.26.7_react-dom@18.3.1_react@18.3.1__react@18.3.1/node_modules/next/dist/build/webpack-config.js
#20 340.9 - /app/node_modules/.pnpm/next@15.1.6_@babel+core@7.26.7_react-dom@18.3.1_react@18.3.1__react@18.3.1/node_modules/next/dist/build/webpack/plugins/next-trace-entrypoints-plugin.js
#20 340.9 - /app/node_modules/.pnpm/next@15.1.6_@babel+core@7.26.7_react-dom@18.3.1_react@18.3.1__react@18.3.1/node_modules/next/dist/build/collect-build-traces.js
#20 340.9 - /app/node_modules/.pnpm/next@15.1.6_@babel+core@7.26.7_react-dom@18.3.1_react@18.3.1__react@18.3.1/node_modules/next/dist/build/index.js
#20 340.9 - /app/node_modules/.pnpm/next@15.1.6_@babel+core@7.26.7_react-dom@18.3.1_react@18.3.1__react@18.3.1/node_modules/next/dist/cli/next-build.js
#20 340.9     at Function.<anonymous> (node:internal/modules/cjs/loader:1244:15)
#20 340.9     at /app/node_modules/.pnpm/next@15.1.6_@babel+core@7.26.7_react-dom@18.3.1_react@18.3.1__react@18.3.1/node_modules/next/dist/server/require-hook.js:55:36
#20 340.9     at Function._load (node:internal/modules/cjs/loader:1070:27)
#20 340.9     at TracingChannel.traceSync (node:diagnostics_channel:322:14)
#20 340.9     at wrapModuleLoad (node:internal/modules/cjs/loader:217:24)
#20 340.9     at Module.<anonymous> (node:internal/modules/cjs/loader:1335:12)
#20 340.9     at mod.require (/app/node_modules/.pnpm/next@15.1.6_@babel+core@7.26.7_react-dom@18.3.1_react@18.3.1__react@18.3.1/node_modules/next/dist/server/require-hook.js:65:28)
#20 340.9     at require (node:internal/modules/helpers:136:16)
#20 340.9     at Object.<anonymous> (/app/node_modules/.pnpm/@tailwindcss+oxide@4.0.4/node_modules/@tailwindcss/oxide/index.js:206:31)
#20 340.9     at Module._compile (node:internal/modules/cjs/loader:1562:14)
#20 340.9 

Hey folks! Are you all using npm or also some other package managers? I’m asking because there’s a known issue right now that platform-specific optional dependencies are not installed right now when doing an npm install with node_modules already present: https://github.com/npm/cli/issues/4828

Some folks have posted workarounds in the lightningcss repo that you could try: https://github.com/parcel-bundler/lightningcss/issues/567.

@t-mart that worked.

I’m using these optional dependencies on ARM now:

"optionalDependencies": {
  "@tailwindcss/oxide-linux-arm64-gnu": "^4.0.1"
},

Manually installing @tailwindcss/oxide-linux-arm64-musl and rerunning yields a new error:

frontend-1  | [Error: Cannot find module '../lightningcss.linux-arm64-musl.node'
frontend-1  | Require stack:
frontend-1  | - /home/node/node_modules/lightningcss/node/index.js
frontend-1  | - /home/node/node_modules/@tailwindcss/postcss/dist/index.js
frontend-1  | - /home/node/node_modules/next/dist/build/webpack/config/blocks/css/plugins.js
frontend-1  | - /home/node/node_modules/next/dist/build/webpack/config/blocks/css/index.js
frontend-1  | - /home/node/node_modules/next/dist/build/webpack/config/index.js
frontend-1  | - /home/node/node_modules/next/dist/build/webpack-config.js
frontend-1  | - /home/node/node_modules/next/dist/server/dev/hot-reloader-webpack.js
frontend-1  | - /home/node/node_modules/next/dist/server/lib/router-utils/setup-dev-bundler.js
frontend-1  | - /home/node/node_modules/next/dist/server/lib/router-server.js
frontend-1  | - /home/node/node_modules/next/dist/server/lib/start-server.js] {
frontend-1  |   code: 'MODULE_NOT_FOUND',
frontend-1  |   requireStack: [Array]
frontend-1  | }

Then I tried installing lightningcss-linux-arm64-musl

npm i lightningcss-linux-arm64-musl

At this point I finally start to get some compilation error tracebacks, but I really doubt that it’s the intention that these packages should have to be manually installed. I suspect there’s some issue detecting which version to install and making it happen along with the default npm i tailwindcss.

I’m still continuing to get some odd deprecation warnings…

frontend-1  | Deprecation Warning on line 44, column 8 of file:///home/node/src/styles/globals.scss:44:8:
frontend-1  | Sass @import rules are deprecated and will be removed in Dart Sass 3.0.0.
frontend-1  |
frontend-1  | More info and automated migrator: https://sass-lang.com/d/import
frontend-1  |
frontend-1  | 44 | @import "tailwindcss";
frontend-1  |
frontend-1  | src/styles/globals.scss 45:9  root stylesheet

and

(node:49) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
(Use `node --trace-deprecation ...` to show where the warning was created)

However, I am able to finally get Tailwind v4.0 “working” after these steps.

EDIT The punycode deprecation warning has nothing to do with Tailwind and appears to stem from ESLint (9.19.x). I discovered by doing npm ls punycode that it is a dependency of another dependency of another dependency used by eslint— uri-js. This package has not been updated in 4 years. Hopefully ESLint can find a way to replace it with something actively maintained.

Hey folks! The next patch release will now include a postinstall script that will attempt to correct this issue if it occurs. This in combination with the npm fix should help reduce the number of times this issue occurs quite drastically: https://github.com/tailwindlabs/tailwindcss/pull/17929

Please let us know if you still run into any issues. 4.1.6 is expected to ship later today 🤞

anybody found a concrete solution

Yup, shared above.

Find missing module via log Install package manually for local, or as a CI/CD step for deployed apps.

npm i

Tell me what your deploy file is if you need a more specific example.

I truly appreciate the assist as I’m both new to Next.js and Docker (years of a ruby dev).

I don’t know if you need the docker-compose.yaml which show the services (mysql, directus backend and my next.js front end).

The Dockerfile is:

FROM --platform=linux/amd64 node:20

# Use a clean working dir
WORKDIR /app

# Prevents cache issues with host node_modules
COPY package.json package-lock.json* ./


# Force npm to build all native modules from source
ENV npm_config_build_from_source=true

# Install dependencies and rebuild lightningcss
RUN npm install --include=optional --verbose \
  && npm rebuild lightningcss --build-from-source --verbose

# Verify the lightningcss binary
RUN ls -l node_modules/lightningcss
RUN ls -l node_modules/lightningcss/node

# Copy all source files AFTER install
COPY . .

# Expose the default dev port
EXPOSE 3000

# Enable .env file
ENV NODE_ENV=development

# Start Next.js in dev mode
CMD ["npm", "run", "dev"]

^ Should I flip to 22?

I’ve even sh’d into the docker instance and deleted the node_modules and npm i, and then npm rebuild lightningcss --build-from-source --verbose

I can see that the module is in there now but still getting the error:

npm verbose cli /Users/grimm/.nvm/versions/node/v18.20.6/bin/node /Users/grimm/.nvm/versions/node/v18.20.6/bin/npm
npm info using npm@10.8.2
npm info using node@v18.20.6
npm verbose title npm rebuild lightningcss
npm verbose argv "rebuild" "lightningcss" "--build-from-source" "--loglevel" "verbose"
npm verbose logfile logs-max:10 dir:/Users/grimm/.npm/_logs/2025-04-14T18_40_23_421Z-
npm verbose logfile /Users/grimm/.npm/_logs/2025-04-14T18_40_23_421Z-debug-0.log
rebuilt dependencies successfully
npm verbose cwd /Users/grimm/Dropbox/_grimmwerks/__WORK/_clients/YIVO/YIVO
npm verbose os Darwin 24.4.0
npm verbose node v18.20.6
npm verbose npm  v10.8.2
npm verbose exit 0
npm info ok


And afterward:

levn					  
lightningcss				  
lightningcss-linux-x64-gnu		  
lightningcss-linux-x64-musl		  
locate-path	

Again, I appreciate the attempt to help; I’ve been trying to figure this thing out for days and going around in circles; if it’s a ME thing feel free to tell me what I’m screwing up here.

I’m really at a loss here; I’ve sh’d into my docker instance and even run

# npm rebuild lightningcss --build-from-source --verbose
npm verbose cli /usr/local/bin/node /usr/local/bin/npm
npm info using npm@10.8.2
npm info using node@v20.19.0
npm verbose title npm rebuild lightningcss
npm verbose argv "rebuild" "lightningcss" "--build-from-source" "--loglevel" "verbose"
npm verbose logfile logs-max:10 dir:/root/.npm/_logs/2025-04-14T16_37_28_161Z-
npm verbose logfile /root/.npm/_logs/2025-04-14T16_37_28_161Z-debug-0.log
rebuilt dependencies successfully
npm verbose cwd /app
npm verbose os Linux 6.10.14-linuxkit
npm verbose node v20.19.0
npm verbose npm  v10.8.2
npm verbose exit 0
npm info ok
# 

I can’t get the proper version of lightningcss to run and it kills my whole frontend; everything runs properly for me locally as npm run but the minute it’s trying to move to docker it borks.

“Same” error for me when trying to update from Tailwind 3 to 4 : Error: Cannot find module '@tailwindcss/oxide-darwin-x64'

I’m using a Mac, it’s a Next.js app. None of the above solution worked for me.

Do you have package-lock.json file, please check if your dependency is listed as an optional dependency. To find the correct binary, which is missing you can run

node -e 'console.log(`npm install --platform=${os.platform()} --arch=${os.arch()} @tailwindcss/postcss`)'

which will return on my Mac M3

npm install --platform=darwin --arch=arm64 @tailwindcss/postcss

and within my node:22-bookworm docker container

npm install --platform=linux --arch=x64 @tailwindcss/postcss

Therefore I need to ensure that my package-lock.json file contains both binaries.

@tehraven that worked for me thank you.

This is a really obscure issue. This has happened so far on local builds and docker builds like others are showing.

Ensuring to remove an existing node_modules, remove package-lock.json and run npm update before npm install resolved my docker image build. It may not be the best way but it worked.

Getting a similar issue on our Jenkins box.

[INFO] $ vite build
[ERROR] failed to load config from /var/lib/jenkins/workspace/ture_ILE-3350-upgrade-tailwind-4/build/web/vite.config.mts
[ERROR] error during build:
[ERROR] Error: Cannot find module '@tailwindcss/oxide-linux-x64-gnu'
[ERROR] Require stack:
[ERROR] - /var/lib/jenkins/workspace/ture_ILE-3350-upgrade-tailwind-4/build/web/node_modules/@tailwindcss/oxide/index.js
[ERROR]     at Function._resolveFilename (node:internal/modules/cjs/loader:1244:15)
[ERROR]     at Function._load (node:internal/modules/cjs/loader:1070:27)
[ERROR]     at TracingChannel.traceSync (node:diagnostics_channel:322:14)
[ERROR]     at wrapModuleLoad (node:internal/modules/cjs/loader:217:24)
[ERROR]     at Module.require (node:internal/modules/cjs/loader:1335:12)
[ERROR]     at require (node:internal/modules/helpers:136:16)
[ERROR]     at Object.<anonymous> (/var/lib/jenkins/workspace/ture_ILE-3350-upgrade-tailwind-4/build/web/node_modules/@tailwindcss/oxide/index.js:190:31)
[ERROR]     at Module._compile (node:internal/modules/cjs/loader:1562:14)
[ERROR]     at Object..js (node:internal/modules/cjs/loader:1699:10)
[ERROR]     at Module.load (node:internal/modules/cjs/loader:1313:32)
[ERROR] error Command failed with exit code 1.

Tried adding but no change.

"optionalDependencies": {
  "@tailwindcss/oxide-linux-x64-gnu": "^4.0.7",
  "lightningcss-linux-x64-gnu": "^1.29.1"
}

using

node version v22.13.0 Yarn version v1.22.22 vite version v6.1.0 tailwind version v4.0.7

I’m seeing the same issue with deno installing in an alpine container on M4 Mac.

9.727 failed to load config from /app/vite.config.ts
9.727 Error during build:
9.728 Error: Cannot find module '../lightningcss.linux-arm64-musl.node'
9.728 Require stack:
9.728 - /app/node_modules/.deno/lightningcss@1.29.1/node_modules/lightningcss/node/index.js
9.728 - /app/node_modules/.deno/lightningcss@1.29.1/node_modules/lightningcss/node/index.js
9.728     at Function.Module._resolveFilename (node:module:619:15)
9.728     at Function.Module._load (node:module:497:27)
9.728     at Module.require (node:module:681:19)
9.728     at require (node:module:812:16)
9.728     at Object.<anonymous> (/app/node_modules/.deno/lightningcss@1.29.1/node_modules/lightningcss/node/index.js:21:22)
9.728     at Object.<anonymous> (/app/node_modules/.deno/lightningcss@1.29.1/node_modules/lightningcss/node/index.js:29:4)
9.728     at Module._compile (node:module:745:34)
9.728     at loadMaybeCjs (node:module:770:10)
9.728     at Object.Module._extensions..js (node:module:755:12)
9.728     at Module.load (node:module:662:32) {
9.728   code: "MODULE_NOT_FOUND",
9.728   requireStack: [
9.728     "/app/node_modules/.deno/lightningcss@1.29.1/node_modules/lightningcss/node/index.js",
9.728     "/app/node_modules/.deno/lightningcss@1.29.1/node_modules/lightningcss/node/index.js"
9.728   ]
[+] Building 0/1
 ⠧ Service app  Building    ```

@l00sed I’m building on an Ampere Altra Max server