Skip to content

Latest commit

 

History

History
executable file
·
60 lines (40 loc) · 1.9 KB

README.md

File metadata and controls

executable file
·
60 lines (40 loc) · 1.9 KB

AIN Connect Extension

Installing and Running

Procedures:

  1. Check if your Node.js version is >= 14.
  2. Clone this repository.
  3. Run yarn install to install the dependencies.
  4. Run yarn start
  5. Load your extension on Chrome following:
    1. Access chrome://extensions/
    2. Check Developer mode
    3. Click on Load unpacked extension
    4. Select the build folder.
  6. Happy hacking.

Webpack auto-reload and HRM

To make your workflow much more efficient this boilerplate uses the webpack server to development (started with yarn start) with auto reload feature that reloads the browser automatically every time that you save some file in your editor.

You can run the dev mode on other port if you want. Just specify the env var port like this:

$ PORT=6002 yarn start

Packing

After the development of your extension run the command

$ NODE_ENV=production yarn 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.

Secrets

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.