Version Packages

packages/vite-plugin/CHANGELOG.md

@@ -1,5 +1,56 @@
 # @crxjs/vite-plugin
 
+## 2.5.0
+
+### Minor Changes
+
+- 4756baf: feat: add HMR support for CSS declared in manifest content_scripts
+- 4756baf: add: browser_specific_settings.gecko properties
+- 4756baf: Fix "TypeError: plugins is not iterable" error when using
+  rolldown-vite (Vite 7).
+
+  In rolldown-vite, the buildStart hook doesn't receive options.plugins. This
+  fix uses the configResolved hook to get plugins from the resolved config, with
+  buildStart kept as a fallback for older Vite versions.
+
+- 4756baf: Fixed
+  [#852](https://github.com/crxjs/chrome-extension-tools/issues/852), the plugin
+  now emits a correct URL in `service-worker-loader.js` when the Vite option
+  `server.https` is enabled.
+- 4756baf: fix: resolve TypeScript types correctly for ESM and CJS consumers
+- 4756baf: feat: add Vite 8 beta support
+
+### Patch Changes
+
+- 4756baf: ci: migrate release workflow to npm trusted publishers
+- 570312a: fix: sanitize colons from output filenames on Windows
+- 4756baf: fix: copy CSS files declared in manifest content_scripts to output
+- 4756baf: Replace cheerio with node-html-parser to fix npm deprecation warning
+  for whatwg-encoding.
+
+  Also adds explicit vite peerDependency declaration (^3.0.0 through ^7.0.0) to
+  enable proper version resolution when used with different vite versions.
+
+- 4756baf: ci: run compat tests against stable Vite 8, make the vite8 available
+  as a peer dependency
+- 4756baf: fix: UnoCSS/TailwindCSS HMR issues with virtual CSS modules
+- 4756baf: fix: respect user's build.manifest setting in Vite 4+
+
+  When users set `build.manifest: false` in their Vite config, the Vite manifest
+  file (`.vite/manifest.json` in Vite 5+, or `manifest.json` in older versions)
+  is now properly removed from the output bundle.
+
+  CRXJS internally requires the Vite manifest to derive content script resources
+  during build, so it forces `build.manifest: true`. Previously, this meant the
+  Vite manifest was always included in the output even if the user explicitly
+  disabled it. Now, CRXJS removes the manifest from the bundle after processing
+  if the user didn't want it.
+
+  Closes #1077
+
+- 4756baf: feat(client): Update the style and content of the development mode
+  loading page
+
 ## 2.3.0
 
 ### Minor Changes

packages/vite-plugin/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@crxjs/vite-plugin",
-  "version": "2.4.0",
+  "version": "2.5.0",
   "description": "Build Chrome Extensions with this Vite plugin.",
   "keywords": [
     "rollup-plugin",