docs: document content script per-browser options#2427
Open
ded-furby 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. |
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
This PR adds a concise docs example for
defineContentScriptshowing per-browser configuration objects for supported options.It demonstrates how fields like
matches,runAt, andworldcan vary by browser in entrypoints (for examplechromevsfirefoxmappings).This addresses issue #2304 by documenting existing
PerBrowsersupport.Manual Testing
npm run check(root) was executed in this repo context, but it fails in this environment duescripts/check-format.jsattempting to read a 2+GiB file (ERR_FS_FILE_TOO_LARGE) before completion.npm run checkinwxtwas executed and completed the initial shared checks, but fails due pre-existing workspace issues:wxt-demoTypeScript problems in unrelated sample/demo files.tsdownconfiguration expects a generated./.wxt/tsconfig.jsonin certain package contexts.No code changes beyond this docs update are included.
Related Issue
Closes #2304