Small cli toolbox for creating cross-browser WebExtensions.
If you want to get started quickly check out the yeoman generator for this project.
chrome
(auto polyfilled)opera
(auto polyfilled)firefox
edge
Works with react.js out of the box!
Run $ npm i react react-dom
and you are ready to go.
The build
task creates bundles for:
- Firefox (
.xpi
) - Chrome (
.zip
) - Opera (
.crx
) - Edge (
.zip
)
Validates your manifest.json
while compiling.
Uses default fields (name
, version
, description
) from your package.json
Allows you to define vendor specific manifest keys.
manifest.json
"name": "my-extension"
"__chrome__key": "yourchromekey"
If the vendor is chrome
it compiles to:
"name": "my-extension"
"key": "yourchromekey"
else it compiles to:
"name": "my-extension"
The webextension standard is currently only supported by firefox and edge. This toolbox adds the necessary polyfills for chrome and opera.
This way many webextension apis will work in chrome and opera out of the box.
In addition to that, this toolbox comes with babel-preset-env.
$ npm install -g webextension-toolbox
- Compiles the extension via webpack to
dist/<vendor>
. - Watches all extension files and recompiles on demand.
- Reloads extension or extension page as soon something changed.
- Sets
process.env.NODE_ENV
todevelopment
. - Sets
process.env.VENDOR
to the current vendor.
$ webextension-toolbox dev <vendor> [..options]
$ webextension-toolbox dev --help
$ webextension-toolbox dev chrome
$ webextension-toolbox dev firefox
$ webextension-toolbox dev opera
$ webextension-toolbox dev edge
- Compile extension via webpack to
dist/<vendor>
. - Minifies extension Code.
- Sets
process.env.NODE_ENV
toproduction
. - Sets
process.env.VENDOR
to the current vendor. - Packs extension to
packages
.
$ webextension-toolbox build <vendor> [..options]
$ webextension-toolbox build --help
$ webextension-toolbox build chrome
$ webextension-toolbox build firefox
$ webextension-toolbox build opera
$ webextension-toolbox build edge
Always use the webextension browser api. Webextension-Toolbox will polyfill it for you in chrome and opera.
All javascript files located at the root of your ./app
or ./app/scripts
directory will create a seperate bundle.
app | dist |
---|---|
app/background.js |
dist/<vendor>/background.js |
app/scripts/background.js |
dist/<vendor>/scripts/background.js |
app/some-dir/some-file.js |
Will be ignored as entry file. |
app/scripts/some-dir/some-file.js |
Will be ignored as entry file. |
In order to extend our usage of webpack
, you can define a function that extends its config via webextension-toolbox.js
.
// This file is not going through babel transformation.
// So, we write it in vanilla JS
// (But you could use ES2015 features supported by your Node.js version)
module.exports = {
webpack: (config, { dev, vendor }) => {
// Perform customizations to webpack config
// Important: return the modified config
return config
}
}
What is the difference to web-ext?
If want to develop browser extensions for Firefox only web-ext might be a better fit for you, since it supports, extension signing, better manifest validation and auto mounting.
Nevertheless if you want to develop cross browser extensions using
- the same development experience in every browser
- a single codebase
- react
- and custom webpack configuration
webextension-toolbox might be your tool of choice.
Copyright 2018 Henrik Wenz
This project is free software released under the MIT license.