Skip to content


Switch branches/tags

Name already in use

A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch?

Latest commit


Git stats


Failed to load latest commit information.
Latest commit message
Commit time

Laser Wallet - A wallet for Helium HNT

This was built using Chrome Extension Boilerplate with React 17 and Webpack 5 as the base.

Installing and Running


  1. Check if your Node.js version is >= 14. .nvmrc is set to v16.1.0 since that's what I've been using in my local dev.
  2. Clone this repository.
  3. Run yarn to install the dependencies.
  4. Run yarn dev
  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.


Anyone of any experience level is welcome to come help. Just follow these guidelines:

  1. Be kind.
  2. If there's something you'd like to help with, create a new issue and let's talk!


The boilerplate is already prepared to have a popup, an options page, a background page, and a new tab page (which replaces the new tab page of your browser).

Webpack auto-reload and HRM

To make your workflow much more efficient this boilerplate uses the webpack server to development (started with npm 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 npm run start

Content Scripts

Although this boilerplate uses the webpack dev server, it's also prepared to write all your bundles files on the disk at every code change, so you can point, on your extension manifest, to your bundles that you want to use as content scripts, but you need to exclude these entry points from hot reloading (why?). To do so you need to expose which entry points are content scripts on the webpack.config.js using the chromeExtensionBoilerplate -> notHotReload config. Look the example below.

Let's say that you want use the myContentScript entry point as content script, so on your webpack.config.js you will configure the entry point and exclude it from hot reloading, like this:

  entry: {
    myContentScript: "./src/js/myContentScript.js"
  chromeExtensionBoilerplate: {
    notHotReload: ["myContentScript"]

and on your src/manifest.json:

  "content_scripts": [
      "matches": ["*"],
      "js": ["myContentScript.bundle.js"]


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:


export default { key: '123' };


import secrets from 'secrets';
ApiCall({ key: secrets.key });

👉 The files with name secrets.*.js already are ignored on the repository.


No description, website, or topics provided.







No releases published


No packages published