Changelog

vitejs/vite · · 6 commits

Config warnings, release branch support

Vite adds native config compatibility warnings, release workflows for v* branches, and a few targeted bug fixes and cleanup.

Warn on unsupported JSON named imports in native config (btea472385e)

Vite now warns when a native-loaded config uses named imports from JSON modules, since JSON only provides a default export per spec. The new compatibility checks cover both relative JSON files and bare package specifiers, while explicitly allowing default as imports.

Warn when applyToEnvironment returns plugins with Vite-only hooks (sapphi-redfdef04f)

Plugins returned from applyToEnvironment or perEnvironmentPlugin now trigger a warning if they define hooks that Vite will ignore there, like config, configEnvironment, configureServer, or configResolved. This makes environment-plugin behavior clearer and should prevent confusion when hooks appear to be “not working.”

Allow releases and publishing from supported v* branches (sapphi-red33d0e98)

The release workflow can now target a specific release branch, validates that branch name, and uses it consistently for checkout and concurrency. Publishing is also enabled for v* branches, which supports backport release flows instead of only main.

Fix srcset parsing for density descriptors without a leading zero (NgoQuocViet2001b50e1b4)

processSrcSetSync now correctly preserves URLs when the density descriptor is written as .5x or .75x. This avoids misparsing valid srcset values that previously could be handled incorrectly.

Other misc changes

  • Removed an unused esbuildPlugin refactor dead code (ulrichstarkf40efef)
  • Updated the repo to pnpm v12 and adjusted workspace settings accordingly (sapphi-red5a38afe)
  • Documentation updates for the new release flow and environment-plugin warning behavior (sapphi-red33d0e98, sapphi-redfdef04f)