AI & Agent Dev Bug Sandbox Back to Radar

Turbopack Asset Rule For CSS Query Url Fails In Server Components

When configuring Turbopack rules to treat `.css?url` imports as asset type, importing from a Server Component fails with 'css client asset is not css chunk placeable'. The same configuration works from Client Components and for other asset types like SVG.

highConfidence 95%Next.js Affected V16.3.8 Affected V16.4.0-Canary.57

Origin Analysis

In the RSC context, every `.css` file is intercepted by `NextCssClientReferenceTransition` before user-defined Turbopack rules are evaluated. This transition matches solely on the file path suffix `.css` and expects the module to be `CssChunkPlaceable`. When a user rule changes the module type to `asset`, the module is no longer `CssChunkPlaceable`, causing the build to fail.

1. Create `next.config.ts` with `turbopack.rules` mapping `*.css` with query `url` to type `asset`. 2. In a Server Component (e.g., `app/layout.tsx`), import `stylesUrl from './styles.css?url'` and use it in a `<link>` tag. 3. Run `next dev` or `next build`. 4. Observe the error `Module not found: Can't resolve './styles.css' ... css client asset is not css chunk placeable`.

Fixing Code Block

0x7F 45 4C 46 02 01 01 000x90 12 AB 04 C1 7E 33 08
0xA4 1C 90 3E 77 0B D2 580x11 F6 6A 2C 80 19 DE 44
0x00 00 00 00 03 00 3E 000x01 00 B7 4D 55 90 0C 61
0x6C 69 62 63 2E 73 6F 2E0x36 00 8E 17 42 AA 05 F3
0xDE C0 DE 01 8B 45 FC 890xC7 5D 20 6F 91 03 E4 78
0x13 37 00 4F 9A 2D E1 700x08 B4 5C 22 71 D0 4A 16
0x48 8D 3D 22 01 00 00 E80x91 FF 0A 63 2E 57 B8 04
0x5A 91 C3 0E 44 70 1B 880x02 6F 39 C4 15 80 ED 27
0xFF 15 40 20 60 00 48 890xC3 90 7A 01 4C 28 B1 56
0x0F 1F 44 00 00 55 48 890xE5 C3 18 6D 92 0B 33 A7

Edge Case Audit

This workaround disables content hashing and cache busting for the stylesheet; manual cache invalidation (e.g., adding a version query parameter) is required when the file changes. It also assumes the CSS is static and does not require processing (e.g., autoprefixing, minification). For production, the proper fix is to upgrade to a Next.js version that skips the CSS transition when a user rule sets a non-CSS type, or conditionally matches on the import query. Rollback is straightforward: remove the public file and revert the import to `./styles.css?url`.