-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Added Manifest V3 compatibility for Firefox #197
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also, https://stackoverflowteams.com/c/expensify/questions/7043/7044#7044 needs updated to use the new build command.
"manifest_version": 3, | ||
|
||
"name": "K2 for GitHub", | ||
"version": "1.3.66", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I believe there are instructions in the README to update this version for every PR. Can you please update the instructions to include this manifest file too?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
done
"description": "A Chrome Extension for Kernel Schedule", | ||
"private": true, | ||
"scripts": { | ||
"preinstall": "./tools/checkRuntimeVersions.sh", | ||
"build": "webpack --progress --config webpack.prod.js", | ||
"build:chrome": "webpack --progress --config webpack.prod.js --env platform=chrome", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is the chrome build necessary? If so, let's be sure to update the README instructions for that too (and maybe remove the build
command completely).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
it's not necessary, but my intention was to leave the default build command as it was, maintaining Chrome compatibility, add a new one for Firefox, and have build:chrome
as an alias for build just for clarity
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Made a change to make it clearer that build
is just an alias for build:chrome
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah, OK. I like the alias change. Thanks!
@youssef-lr I'm gonna go ahead and merge this |
@mjasikowski It's got a new error now: The link points to: https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/manifest.json |
@tgolen nice, new error means progress! |
Added a separate build script for Firefox (
npm run build:firefox
) that usesmanifest-firefox.json
instead of the defaultmanifest.json
. Since FIrefox has no background worker support, we had to fall back to standard background script for that instead.Usage:
-
npm run build
ornpm run build:chrome
builds the Chrome compatible version in dist-
npm run build:firefox
builds the Firefox compatible version in dist