Build: Update Vite to 8.3.2 and remove the PostCSS browser resolver - #83992
Merged
Merged
Conversation
🤖 PR meta 🤖🎉 PropsIf you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message. To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. Updated as activity occurs, without notifying anyone named here. Add the 📦 Bundle sizeSize Change: 0 B Total Size: 8.25 MB
⚡ PerformanceShow the resultsClient side metrics exclude the server response time. front-end-block-theme
front-end-classic-theme
media-processing
media-upload
post-editor
site-editor
|
9 of 18 tasks
widoz
pushed a commit
to widoz/gutenberg
that referenced
this pull request
Oct 2, 2026
…ordPress#83992) * Build: Update Vite to 8.3.2 and remove the PostCSS browser resolver * Theme: Document the Vite development dependency update --- Co-authored-by: ciampo <mciampini@git.wordpress.org> Co-authored-by: Mamaduka <mamaduka@git.wordpress.org>
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.
Follow-up to #83091 and #83635.
What?
Update Vite to 8.3.2 and remove the temporary PostCSS browser resolver from Browser Mode and Storybook.
Why?
Vite 8.3.2 includes the upstream fix for browser-externalized warnings when PostCSS probes imports mapped to
falsein its browser configuration.How?
Update the three Vite development dependencies and the shared lockfile resolution. Delete the resolver and both registrations. Retain the Browser Mode regression for CSS transformation and asset URL rebasing, and the Storybook static smoke checks.
Testing Instructions
npm ciandnpm run build.npm run test:unit:vitest:shuffled -- --sequence.seed=20261001 --project=browser. The retained PostCSS regression must pass, including selector scoping and asset URL rebasing, without browser-externalized warnings.NODE_ENV=test npm run storybook:build, thennpm run --workspace @wordpress/storybook test:smoke. All built stories should render with successful asset requests, and the Chromium story tests should pass without browser-externalized warnings.Local verification
20261001: 1,691 tests passed and 72 expected failures.fromwarning still appears in Browser Mode. It was already documented alongside the resolver and remains outside this browser-externalized warning fix.Bug Fixessection in the unchanged DataViews changelog.npm auditreports the same 53 existing advisories before and after the update, with none for Vite or Rolldown.Use of AI Tools
Codex implemented the dependency and configuration changes, ran local verification, and drafted this description.