You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Migrate Chrome and Edge builds to Manifest V3 (#269)
* Migrate Chrome and Edge builds to Manifest V3
Chrome and Edge now build MV3 by default (Firefox stays MV2):
- Drop --mv2 from the chrome/edge build, zip, and start scripts
- Branch the manifest on manifestVersion: action replaces page_action,
host permissions move to host_permissions, web_accessible_resources
uses the MV3 object format, and minimum_chrome_version becomes 88
- Make the background persistent flag MV2-only (MV3 uses a service worker)
- Emulate the old page action behavior on MV3 with the action API:
disable the toolbar button globally on install/startup and enable it
per-tab on deviantart.com; Firefox keeps the real pageAction API
- Replace the removed extension.getURL with runtime.getURL
- Update the manifest smoke tests to assert the chrome-mv3/edge-mv3
outputs (MV3 shape) alongside the unchanged firefox-mv2 output
* Set per-browser transpilation targets for built bundles
Vite/esbuild ignore the browserslist field and default to a ~es2020
target, so the firefox build shipped untranspiled optional chaining
(?.), nullish coalescing (??), and logical nullish assignment (??=),
none of which Firefox 62 (the declared strict_min_version) supports.
Set the esbuild target explicitly: firefox62 for the Firefox build and
chrome88 for the Chrome/Edge MV3 builds.
0 commit comments