[PR #850] [MERGED] fix: exclude @tailwindcss/oxide from dep optimization #896

New issue

Closed

opened 2026-05-06 13:10:43 +02:00 by BreizhHardware · 0 comments

BreizhHardware commented

2026-05-06 13:10:43 +02:00

Owner

📋 Pull Request Information

Original PR: https://github.com/cloudflare/vinext/pull/850
Author: @467469274
Created: 4/15/2026
Status: ✅ Merged
Merged: 4/16/2026
Merged by: @james-elicx

Base: main ← Head: feat/add-missing-shims-and-fixes

📝 Commits (1)

f9b0c68 fix: exclude @tailwindcss/oxide from dep optimization

📊 Changes

1 file changed (+2 additions, -1 deletions)

View changed files

📝 packages/vinext/src/index.ts (+2 -1)

📄 Description

Summary

Exclude @tailwindcss/oxide from Vite's dependency optimization — Rolldown cannot process native .node binaries.

Problem

Rolldown cannot process native .node binary files. When a project uses Tailwind CSS v4, @tailwindcss/oxide contains platform-specific native bindings (tailwindcss-oxide.darwin-arm64.node) that cause Rolldown to fail with UNLOADABLE_DEPENDENCY during dependency optimization.

Error:

[UNLOADABLE_DEPENDENCY] Error: Could not load @tailwindcss/oxide-darwin-arm64/tailwindcss-oxide.darwin-arm64.node
  stream did not contain valid UTF-8

Fix

Added @tailwindcss/oxide to the default optimizeDeps.exclude list alongside vinext and @vercel/og.

Changes

Dropped the next/navigation default export per review feedback — Next.js itself does not provide a default export from next/navigation, and the stated @clerk/nextjs use case was incorrect (Clerk uses named imports).

Test plan

Reproduced with Vite 8.0.8 + Rolldown 1.0.0-rc.15 + @tailwindcss/vite 4.2.2
Tested against next-shadcn-dashboard-starter (Next.js 16, Tailwind v4)
Run existing test suite

🤖 Generated with Claude Code

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/cloudflare/vinext/pull/850 **Author:** [@467469274](https://github.com/467469274) **Created:** 4/15/2026 **Status:** ✅ Merged **Merged:** 4/16/2026 **Merged by:** [@james-elicx](https://github.com/james-elicx) **Base:** `main` ← **Head:** `feat/add-missing-shims-and-fixes` --- ### 📝 Commits (1) - [`f9b0c68`](https://github.com/cloudflare/vinext/commit/f9b0c68fdb3f3b7b2e83fc1e13c820561cd7b93c) fix: exclude @tailwindcss/oxide from dep optimization ### 📊 Changes **1 file changed** (+2 additions, -1 deletions) <details> <summary>View changed files</summary> 📝 `packages/vinext/src/index.ts` (+2 -1) </details> ### 📄 Description ## Summary Exclude `@tailwindcss/oxide` from Vite's dependency optimization — Rolldown cannot process native `.node` binaries. ## Problem Rolldown cannot process native `.node` binary files. When a project uses Tailwind CSS v4, `@tailwindcss/oxide` contains platform-specific native bindings (`tailwindcss-oxide.darwin-arm64.node`) that cause Rolldown to fail with `UNLOADABLE_DEPENDENCY` during dependency optimization. **Error:** ``` [UNLOADABLE_DEPENDENCY] Error: Could not load @tailwindcss/oxide-darwin-arm64/tailwindcss-oxide.darwin-arm64.node stream did not contain valid UTF-8 ``` ## Fix Added `@tailwindcss/oxide` to the default `optimizeDeps.exclude` list alongside `vinext` and `@vercel/og`. ## Changes Dropped the `next/navigation` default export per review feedback — Next.js itself does not provide a default export from `next/navigation`, and the stated `@clerk/nextjs` use case was incorrect (Clerk uses named imports). ## Test plan - [x] Reproduced with Vite 8.0.8 + Rolldown 1.0.0-rc.15 + @tailwindcss/vite 4.2.2 - [x] Tested against [next-shadcn-dashboard-starter](https://github.com/Kiranism/next-shadcn-dashboard-starter) (Next.js 16, Tailwind v4) - [ ] Run existing test suite 🤖 Generated with [Claude Code](https://claude.com/claude-code) --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>