Open
Conversation
🦋 Changeset detectedLatest commit: d97e33a The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
Contributor
Contributor trust score43/100 — Moderate This score estimates contributor familiarity with Outcome
Score breakdown
Signals used
Policy
Updated automatically when the PR changes or when a maintainer reruns the workflow. |
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.
Summary
wxtfrom0.20.20to0.20.21DOTENV_CONFIG_QUIET=falseprefixes from WXT build/dev/zip scripts now that WXT handles env loading nativelywxt.config.tsby disabling React plugin OXC overrides and escaping problematic code points during bundle generationWhy
WXT 0.20.21 includes an ASCII-output fix for extension bundles, but in this repo Vite 8 +
@vitejs/plugin-reactv6 can still force OXC and bypass that protection. This PR keeps the dependency upgrade while making sure the final extension bundles do not contain rawU+2028,U+2029,U+FEFF, orU+FFFFcharacters.Validation
pnpm install --frozen-lockfilepnpm buildpnpm build:firefoxpnpm type-checkSKIP_FREE_API=true pnpm test.output/chrome-mv3/**/*.jsand.output/firefox-mv3/**/*.jsto confirm there are no remaining rawU+2028,U+2029,U+FEFF, orU+FFFFcode pointsSummary by cubic
Upgrade
wxtto 0.20.21 and keep extension bundles ASCII-only to avoid invalid code points in MV3 builds. Also remove legacy dotenv flags from scripts and add a changeset.Bug Fixes
oxcfrom@vitejs/plugin-reactso WXT’s ASCII output stays effective.U+2028,U+2029,U+FEFF, andU+FFFFin emitted.jschunks during bundle generation.Dependencies
wxtto0.20.21and updatepnpm-lock.yaml.DOTENV_CONFIG_QUIET=falsefrom build/dev/zip scripts sincewxtloads env vars natively.Written for commit d97e33a. Summary will update on new commits.