From 7c5b7502644ad1dde8b48e7b81979fd57f2d32b9 Mon Sep 17 00:00:00 2001 From: Ajay Ramachandran Date: Tue, 1 Aug 2023 19:57:07 -0400 Subject: [PATCH] use npm ci for consistency --- CONTRIBUTING.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 4f94363e..c337879d 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -14,7 +14,7 @@ If you make any contributions to SponsorBlock after this file was created, you a 2. Copy the file `config.json.example` to `config.json` and adjust configuration as desired. - Comments are invalid in JSON, make sure they are all removed. - You will need to repeat this step in the future if you get build errors related to `CompileConfig` or `property does not exist on type ConfigClass`. This can happen for example when a new category is added. -3. Run `npm install` in the repository to install dependencies. +3. Run `npm ci` in the repository to install dependencies. 4. Run `npm run build:dev` (for Chrome) or `npm run build:dev:firefox` (for Firefox) to generate a development version of the extension with source maps. - You can also run `npm run build` (for Chrome) or `npm run build:firefox` (for Firefox) to generate a production build. 5. The built extension is now in `dist/`. You can load this folder directly in Chrome as an [unpacked extension](https://developer.chrome.com/docs/extensions/mv3/getstarted/#manifest), or convert it to a zip file to load it as a [temporary extension](https://developer.mozilla.org/docs/Tools/about:debugging#loading_a_temporary_extension) in Firefox.