The main idea of creating this extension for Chrome is to count how many times localhost gets reloaded during development.
It uses window.perfromance
API to collect data not only for localhost but for all domains which gets reloaded while surfing Internet.
This project was created with help of chrome-extension-webpack-boilerplate
Samuel Simões ~ @samuelsimoes ~ Blog
I'll assume that you already read the Webpack docs and the Chrome Extension docs.
- Check if your Node.js version is >= 6.
- Clone the repository.
- Install yarn.
- Run
yarn
. - Change the package's name and description on
package.json
. - Change the name of your extension on
src/manifest.json
. - Run
npm run start
- Load your extension on Chrome following:
- Access
chrome://extensions/
- Check
Developer mode
- Click on
Load unpacked extension
- Select the
build
folder.
- Access
- Have fun.
You can run the dev mode on other port if you want. Just specify the env var port
like this:
$ PORT=6002 yarn run start
After the development of your extension run the command
$ NODE_ENV=production npm run build
Now, the content of build
folder will be the extension ready to be submitted to the Chrome Web Store. Just take a look at the official guide to more infos about publishing.
If you are developing an extension that talks with some API you probably are using different keys for testing and production. Is a good practice you not commit your secret keys and expose to anyone that have access to the repository.
To this task this boilerplate import the file ./secrets.<THE-NODE_ENV>.js
on your modules through the module named as secrets
, so you can do things like this:
./secrets.development.js
export default { key: "123" };
./src/popup.js
import secrets from "secrets";
ApiCall({ key: secrets.key });
👉 The files with name secrets.*.js
already are ignored on the repository.