From 74ff5951f1b446b77bc06b5cc5e67d65f4f81d7f Mon Sep 17 00:00:00 2001 From: Erin Date: Fri, 9 Sep 2022 13:51:44 -0400 Subject: [PATCH 1/3] Add release build script --- package.json | 1 + 1 file changed, 1 insertion(+) diff --git a/package.json b/package.json index 55662ccc2..b11dd0425 100644 --- a/package.json +++ b/package.json @@ -6,6 +6,7 @@ "scripts": { "build": "rollup -c rollup.config.js", "build:watch": "rollup -c rollup.config.js --watch", + "build:release": "npm ci && cross-env NODE_ENV=production rollup -c rollup.config.js", "eslint": "eslint . --config .eslintrc.json --ignore-path .eslintignore", "docs": "jsdoc -c jsdoc.json" }, From 636118250f42e9d0ef2c4e8e3db1c4782ab94163 Mon Sep 17 00:00:00 2001 From: Erin Date: Fri, 9 Sep 2022 14:01:20 -0400 Subject: [PATCH 2/3] add basic dependabot.yml --- .github/dependabot.yml | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 .github/dependabot.yml diff --git a/.github/dependabot.yml b/.github/dependabot.yml new file mode 100644 index 000000000..49468ff9b --- /dev/null +++ b/.github/dependabot.yml @@ -0,0 +1,8 @@ +version: 2 +updates: + - package-ecosystem: npm + directory: / + schedule: + interval: daily + labels: + - dependencies From eb5ade413b20fd5b045acad7305e5c88daf70e3c Mon Sep 17 00:00:00 2001 From: Erin Date: Fri, 9 Sep 2022 14:13:06 -0400 Subject: [PATCH 3/3] Document new build:release script --- CONTRIBUTING.md | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 7a980f72f..e55234f85 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -55,10 +55,11 @@ You can find the documentation for all this on the following locations: Building the extension is relatively easy through [Node.js](https://nodejs.org/en/). We use [Rollup](https://www.rollupjs.org/) to bundle the extension's Javascript code and manually copy over assets including images and the `manifest.json` file via [rollup-plugin-copy](https://www.npmjs.com/package/rollup-plugin-copy). Additionally, some browser-specific processing is applied to the manifest to work around some browser-specific incompatibilities. Build output goes to `build/chrome` and `build/firefox`. ```sh -$ npm install # Install dependencies -$ npm run build # Build extension -$ npm run build:watch # Automatically rebuild on file changes -$ npm run docs # Build documentation of internal interfaces +$ npm install # Install dependencies +$ npm run build # Build extension +$ npm run build:watch # Automatically rebuild on file changes +$ npm run build:release # Install dependencies and perform a release build +$ npm run docs # Build documentation of internal interfaces ``` Once you've built the extension, you can load it up in your browser for testing: