fix: exclude @tailwindcss/oxide from dep optimization + add navigation default export#850
Open
467469274 wants to merge 1 commit intocloudflare:mainfrom
Open
fix: exclude @tailwindcss/oxide from dep optimization + add navigation default export#850467469274 wants to merge 1 commit intocloudflare:mainfrom
467469274 wants to merge 1 commit intocloudflare:mainfrom
Conversation
…n default export ## @tailwindcss/oxide exclusion Rolldown cannot process native `.node` binary files. When a project uses Tailwind CSS v4, the `@tailwindcss/oxide` package contains platform-specific native bindings (`tailwindcss-oxide.darwin-arm64.node`) that cause Rolldown to fail with `UNLOADABLE_DEPENDENCY` during dependency optimization. Added `@tailwindcss/oxide` to the default `optimizeDeps.exclude` list alongside `vinext` and `@vercel/og`. Reproduction: any project with `@tailwindcss/vite` or `@tailwindcss/postcss` installed, running on Vite 8 with Rolldown. ## next/navigation default export Some third-party libraries use `import navigation from 'next/navigation'` (default import) instead of named imports. The navigation shim only had named exports, causing `SyntaxError: does not provide an export named 'default'`. Added a default export object containing all standard Next.js navigation APIs (useRouter, usePathname, useSearchParams, redirect, notFound, etc.). Found while testing vinext against next-shadcn-dashboard-starter (https://github.com/Kiranism/next-shadcn-dashboard-starter).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
@tailwindcss/oxidefrom Vite's dependency optimization — Rolldown cannot process native.nodebinariesnext/navigationshim for third-party library compatibility@tailwindcss/oxide exclusion
Rolldown cannot process native
.nodebinary files. When a project uses Tailwind CSS v4,@tailwindcss/oxidecontains platform-specific native bindings (tailwindcss-oxide.darwin-arm64.node) that cause Rolldown to fail withUNLOADABLE_DEPENDENCYduring dependency optimization.Error:
Fix: Added
@tailwindcss/oxideto the defaultoptimizeDeps.excludelist alongsidevinextand@vercel/og.next/navigation default export
Some third-party libraries (e.g.
@clerk/nextjs) useimport navigation from 'next/navigation'(default import) instead of named imports. The navigation shim only had named exports, causing:Fix: Added a default export object containing all standard Next.js navigation APIs.
Test plan
🤖 Generated with Claude Code