Track Jira tickets by day and web activity for easier time tracking

Open a terminal in cloned repo directory and install all NodeJS dependencies with npm or

npm install

Start the continuous build process to transpile the code into something that can run in Firefox or Chrome:

npm run build:dev

This creates a WebExtension in the extension subdirectory. Any time you edit a file, it will be rebuilt automatically.

In another shell window, run the extension in Firefox using a wrapper around web-ext:

npm start

Any time you edit a file, web-ext will reload the extension in Firefox.

npm run build:prod

This packs and transpiles the source with NODE_ENV='production' and creates an unsigned extension zip package in WEB_EXT_ARTIFACTS_DIR

General Notes

• web-ext uses the name and version values from the extension's manifest.json (not package.json) when packaging the extension
• version number should be incremented using semantic versioning rules - if version has not been incremented from last successful upload then sign/upload will fail

Sign/Upload scripting for Firefox uses the web-ext package and requires valid addon API credentials for an AMO developer account that is assigned as an owner or developer of the extension.

Use upload:firefox npm script to package, sign, and upload the contents of WEB_EXT_SOURCE_DIR

npm run upload:firefox -- --api-key=$WEB_EXT_API_KEY --api-secret=$WEB_EXT_API_SECRET

If WEB_EXT_API_KEY and WEB_EXT_API_SECRET are defined in ./firefox.env or local environment then shortened syntax can be used instead

npm run upload:firefox

Sign/Upload scripting for Chrome uses the chrome-webstore-upload-cli package and requires valid webstore API OAuth credentials for a google developer account that is a member of the extension publishing group.

Use upload:chrome npm script to sign and upload the prebuilt zip package from WEB_EXT_ARTIFACTS_DIR

npm run upload:chrome -- --client_id=$CLIENT_ID --client_secret=$CLIENT_SECRET --refresh_token=$REFRESH_TOKEN

If CLIENT_ID, CLIENT_SECRET, and REFRESH_TOKEN are defined in ./chrome.env or local environment then shortened syntax can be used instead

npm run upload:chrome