fix(build): map CSS chunks in chunk import maps (fix #22946) - #22947
Merged
Merged
Conversation
sapphi-red
approved these changes
Jul 17, 2026
sapphi-red
left a comment
Member
There was a problem hiding this comment.
Thanks!
I added a new test case and some comments clarifying the behavior.
7 tasks done
3 tasks
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
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.
Fixes #22946
When
build.chunkImportMapis enabled, dynamic JavaScript dependencies use stable import-map specifiers, but extracted CSS dependencies still use content-hashed filenames. A CSS-only change can therefore leave a parent chunk filename unchanged while changing its cached preload array.This tracks each emitted CSS asset's originating chunk, adds a corresponding stable CSS entry to the generated import map, and lets preload rewriting use that stable specifier. Builds without
chunkImportMapare unchanged.I considered rewriting only the preload array or changing global asset filenames. The former would not give the browser a target mapping, while the latter would affect unrelated builds. Extending the generated import map keeps the change scoped to the experimental option.
Tests:
pnpm run buildpnpm run test-build chunk-importmappnpm exec eslint packages/vite/src/node/plugins/css.ts packages/vite/src/node/plugins/html.ts playground/chunk-importmap/__tests__/chunk-importmap.spec.ts