Open
Conversation
github-actions
bot
force-pushed
the
changeset-release/main
branch
3 times, most recently
from
5c3633f to
bc0355e
Compare
github-actions
bot
force-pushed
the
changeset-release/main
branch
2 times, most recently
from
0673a3d to
6555b22
Compare
github-actions
bot
force-pushed
the
changeset-release/main
branch
from
6555b22 to
fc25912
Compare
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.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@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, the plugin
now emits a correct URL in
service-worker-loader.jswhen the Vite optionserver.httpsis 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: falsein their Vite config, the Vite manifestfile (
.vite/manifest.jsonin Vite 5+, ormanifest.jsonin 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 theVite 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 Vite plugin ignores vite manifest setting #1077
4756baf: feat(client): Update the style and content of the development mode
loading page