Can't install @tailwindcss/oxide

[Guendi]

It gets stuck here. I waited for 30min nothing happend.
I just deleted all node_modules to get a clean installation and after that, it is not working anymore

[4/4] Building fresh packages...
[-/6] ⠄ waiting...
[-/6] ⠄ waiting...
[3/6] ⠄ @tailwindcss/oxide
[-/6] ⡀ waiting...
[-/6] ⡀ waiting...

Node.js v22.18.0.
Nextjs: 15.4.5
yarn: v1.22.22
Windows 11: x86
tailwind: 4.1.8

[victormoni]

Hi @Guendi

Can't install @tailwindcss/oxide — quick fixes (Windows)

It usually stalls on Windows when the native Oxide binary can’t be downloaded or doesn’t match your CPU/Node architecture. Try these in order:

1) Confirm you’re on 64‑bit Node and OS

Oxide publishes a win32‑x64 binary — 32‑bit (ia32) isn’t supported.

node -p "process.platform + ' ' + process.arch"
# expect: win32 x64  (if you see ia32, install 64‑bit Node/OS)

Ref: npm package for the Windows x64 build shows the target: x86_64-pc-windows-msvc.
https://www.npmjs.com/package/@tailwindcss/oxide-win32-x64-msvc

2) Clear caches and reinstall

# from your project root
rd /s /q node_modules  # or: rm -rf node_modules
del yarn.lock          # or: del package-lock.json
yarn cache clean       # or: npm cache clean --force
yarn install           # or: npm install / pnpm install

If Yarn 1 keeps hanging at “Building fresh packages…”, try npm or pnpm instead (some users report Yarn 1 getting stuck on postinstall scripts).
Refs: related Windows/Oxide reports and workarounds:

• Tailwind team discussion (Windows/Oxide binary issues): Struggling with Tailwind v4.0 on a fresh windows installation #15701
• Another Oxide install thread: \node_modules\@tailwindcss\oxide-win32-x64-msvc\tailwindcss-oxide.win32-x64-msvc.node'. Please verify that the package.json has a valid "main" entry #15849

3) Check corporate proxy / antivirus

Network filters can block the postinstall that downloads the Oxide binary. If you’re behind a proxy/VPN, set your npm/yarn proxy and try again:

npm config set proxy http://your-proxy:port
npm config set https-proxy http://your-proxy:port

Or temporarily disable the filter and retry.

4) Force a rebuild of native deps

npm rebuild @tailwindcss/oxide --foreground-scripts
# or with yarn
yarn add -D @tailwindcss/oxide --force

5) (Temporary) fall back if you just need to keep working

Tailwind v4 is powered by Oxide, but you can temporarily fall back to avoid the native binary while you investigate. (See Tailwind v4/Oxide background below.)

Tip: After getting a successful install, re‑enable Oxide for best performance.

Extra context / reading

• Tailwind v4 announcement (Oxide engine intro): https://tailwindcss.com/blog/tailwindcss-v4
• Earlier Oxide background: https://tailwindcss.com/blog/tailwindcss-v4-alpha
• Windows x64 Oxide binary on npm: https://www.npmjs.com/package/@tailwindcss/oxide-win32-x64-msvc
• More Windows/Oxide install discussions:
  • Struggling with Tailwind v4.0 on a fresh windows installation #15701
  • Tailwind CSS v4.x (@tailwindcss/oxide) native binary not installing on WSL2 / Win 11 Pro, postinstall script reports success but file is missing. #18427

---

If it’s still stuck

Please share the output of:

node -v
npm -v && yarn -v
node -p "process.platform + ' ' + process.arch"
setx # (or `set`/`env` list to check proxies)

…and we can narrow it down (arch mismatch vs. network vs. toolchain).

[Guendi]

installing Node x64 worked for me.

Thanks