When actively developing the extension you can use start to have Webpack watch for changes and automatically recompile the extension.
$ npm run startYou can also build the project without it watching for change by using build:dev
$ npm run build:devAfter adding translations to the messages .json files in ./src/_locales, you'll need to reload the extension in chrome://extensions for them to take affect.
Sorry, there aren't any. I wrote this in a couple of nights and during a long haul flight.
This is more notes for myself so I don't forget this manual process.
- Squash and merge PR branch
- Pull master locally
- Run
npm version <major|minor|patch> - Check version in
manifest.jsonhas been automatically updated - Commit amend
- Push!
- Draft release with new tag