填資料是快樂的事,不用填資料是更快樂的事
49 & later ✔ | 52 & later ✔ | 36 & later ✔ | 79 & later ✔ | Latest ✔ | Latest ✔ | Latest ✔ |
Ensure you have
Then run the following:
npm install
to install dependencies.npm run dev:chrome
to start the development server for chrome extensionnpm run dev:firefox
to start the development server for firefox addonnpm run dev:opera
to start the development server for opera extensionnpm run build:chrome
to build chrome extensionnpm run build:firefox
to build firefox addonnpm run build:opera
to build opera extensionnpm run build
builds and packs extensions all at once to extension/ directory
-
npm install
to install dependencies. -
To watch file changes in development
- Chrome
npm run dev:chrome
- Firefox
npm run dev:firefox
- Opera
npm run dev:opera
- Chrome
-
Load extension in browser
-
- Go to the browser address bar and type
chrome://extensions
- Check the
Developer Mode
button to enable it. - Click on the
Load Unpacked Extension…
button. - Select your extension’s extracted directory.
- Go to the browser address bar and type
-
- Load the Add-on via
about:debugging
as temporary Add-on. - Choose the
manifest.json
file in the extracted directory
- Load the Add-on via
-
- Load the extension via
opera:extensions
- Check the
Developer Mode
and load as unpacked from extension’s extracted directory.
- Load the extension via
npm run build
builds the extension for all the browsers toextension/BROWSER
directory respectively.
Note: By default the manifest.json
is set with version 0.0.0
. The webpack loader will update the version in the build with that of the package.json
version. In order to release a new version, update version in package.json
and run script.
If you don't want to use package.json
version, you can disable the option here.
Please file an issue here for bugs, missing documentation, or unexpected behavior.