fix: preserve matchOriginAsFallback in dev scripts#2437
Open
cookesan wants to merge 1 commit into
Open
Conversation
✅ Deploy Preview for creative-fairy-df92c4 ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
github-actions
Bot
added
the
pkg/wxt
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
1 participant
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.
Overview
Preserves
matchOriginAsFallbackwhen WXT maps content script options into the MV3 registered content script payload used during dev reloads.Chrome and the generated browser types support
matchOriginAsFallbackforscripting.RegisteredContentScript, whilematchAboutBlank,includeGlobs, andexcludeGlobsstay manifest-only options.Manual Testing
bun run --filter wxt test run content-scriptsbun run --filter wxt checkbun run --filter wxt test runbun run checkbun run testRelated Issue
This PR closes #2335