|1 year ago|
|config||4 years ago|
|resources||4 years ago|
|src||1 year ago|
|.babelrc||4 years ago|
|.editorconfig||4 years ago|
|.gitignore||3 years ago|
|LICENSE.txt||4 years ago|
|README.md||1 year ago|
|gulpfile.babel.js||3 years ago|
|manifest.json||1 year ago|
|package.json||2 years ago|
|privacy_policy.md||1 year ago|
|yarn.lock||2 years ago|
ReadLaterByEmail webextension generator
📚 Table of Contents
First check if you have composer installed
Before installing this, you need to check if you have
NPM installed on your computer.
Then install this script
git clone ssh://firstname.lastname@example.org:2200/ReadLaterByEmail/webextensions.git cd webextensions npm install npm run build
Load the extension in Chrome & Opera
- Open Chrome/Opera browser and navigate to chrome://extensions
- Select "Developer Mode" and then click "Load unpacked extension..."
- From the file browser, choose to
Load the extension in Firefox
- Open Firefox browser and navigate to about:debugging
- Click "Load Temporary Add-on" and from the file browser, choose
The following tasks can be used when you want to start developing the extension and want to enable live reload -
npm run chrome-watch
npm run opera-watch
npm run firefox-watch
npm run dist to create a zipped, production-ready extension for each browser. You can then upload that to the appstore.
npm run sourcezip for firefox submission
- Write once and deploy to Chrome, Opera & Firefox
- Based on WebExtensions. It also includes a tiny polyfill to bring uniformity to the APIs exposed by different browsers.
- Your changes to CSS, HTML & JS files will be relayed instantly without having to manually reload the extension. This ends up saving a lot of time and improving the developer experience.
- Sensible starting point
- Sketch (.sketch) assets for icons and promo images
- A .sketch file is included in the resources directory. This has all the icons and promo images that will be needed while uploading the extensions to the app stores.
- Easily configurable and extendable
- The gulpfile is easily understandable and configurable. If you want to add additional tasks or remove un-used ones, you can easily tweak that file to suit your needs.
- Platform specific & Environment specific variables.
You might need to specify different data variables based on your environment. For example, you might want to use a localhost API endpoint during development and a production API endpoint once the extension is submitted to the appstore. You can specify such data in the json files inside `config` directory.
You can also set custom data variables based on the platform (different variable for Chrome, FF, Opera).
Please open an issue for support.
Based on Email This which is licensed under the MIT license.