Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/next2golang/com-wallet
https://github.com/next2golang/com-wallet
Last synced: 3 days ago
JSON representation
- Host: GitHub
- URL: https://github.com/next2golang/com-wallet
- Owner: next2golang
- License: mit
- Created: 2024-03-08T19:44:27.000Z (10 months ago)
- Default Branch: main
- Last Pushed: 2024-03-21T15:59:27.000Z (9 months ago)
- Last Synced: 2024-11-02T06:03:03.262Z (about 2 months ago)
- Language: TypeScript
- Size: 585 KB
- Stars: 2
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# Wallet Extension with React 18 and Webpack 5
[](https://www.npmjs.com/package/chrome-extension-boilerplate-react)
[](https://www.npmjs.com/package/chrome-extension-boilerplate-react)
[](https://www.npmjs.com/package/chrome-extension-boilerplate-react)
[](https://david-dm.org/lxieyang/chrome-extension-boilerplate-react)
[](https://david-dm.org/lxieyang/chrome-extension-boilerplate-react?type=dev)
## Features
This is a wallet chrome extension with both popup and onboard inspired by metamask
Used boilerplate of this guy: Michael Xieyang Liu | [Website](https://lxieyang.github.io).
Refactored the structure of his boilerplate and moved:
From React 17 to React 18
From SCSS to Tailwind CSS
The extension is updated with:
- [Chrome Extension Manifest V3](https://developer.chrome.com/docs/extensions/mv3/intro/mv3-overview/)
- [React 18](https://reactjs.org)
- [Webpack 5](https://webpack.js.org/)
- [React Hot Loader](https://github.com/gaearon/react-hot-loader)
- [eslint-config-react-app](https://www.npmjs.com/package/eslint-config-react-app)
- [Prettier](https://prettier.io/)
- [TypeScript](https://www.typescriptlang.org/)
The extension is heavily inspired by and adapted from [https://github.com/samuelsimoes/chrome-extension-webpack-boilerplate](https://github.com/samuelsimoes/chrome-extension-webpack-boilerplate), with additional support for React 17 features and Webpack 5.
### Procedures:
1. Check if your [Node.js](https://nodejs.org/) version is >= **14**.
2. Clone this repository.
3. Change the package's `name`, `description`, and `repository` fields in `package.json`.
4. Change the name of your extension on `src/manifest.json`.
5. Run `npm install` to install the dependencies.
6. Run `npm start`
7. 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.
8. Happy hacking.
## Structure
All your extension's code must be placed in the `src` folder.
## Webpack auto-reload and HRM
To make your workflow much more efficient this boilerplate uses the [webpack server](https://webpack.github.io/docs/webpack-dev-server.html) 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](https://developer.chrome.com/extensions/content_scripts), but you need to exclude these entry points from hot reloading [(why?)](https://github.com/samuelsimoes/chrome-extension-webpack-boilerplate/issues/4#issuecomment-261788690). 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:
```js
{
…
entry: {
myContentScript: "./src/js/myContentScript.js"
},
chromeExtensionBoilerplate: {
notHotReload: ["myContentScript"]
}
…
}
```
and on your `src/manifest.json`:
```json
{
"content_scripts": [
{
"matches": ["https://www.google.com/*"],
"js": ["myContentScript.bundle.js"]
}
]
}
```
## Intelligent Code Completion
Thanks to [@hudidit](https://github.com/lxieyang/chrome-extension-boilerplate-react/issues/4)'s kind suggestions, this boilerplate supports chrome-specific intelligent code completion using [@types/chrome](https://www.npmjs.com/package/@types/chrome). For example:
## Packing
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](https://developer.chrome.com/webstore/publish) 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..js` on your modules through the module named as `secrets`, so you can do things like this:
_./secrets.development.js_
```js
export default { key: '123' };
```
_./src/popup.js_
```js
import secrets from 'secrets';
ApiCall({ key: secrets.key });
```
:point_right: The files with name `secrets.*.js` already are ignored on the repository.
## Resources:
- [Webpack documentation](https://webpack.js.org/concepts/)
- [Chrome Extension documentation](https://developer.chrome.com/extensions/getstarted)
---