- Backpack is in active development, so all APIs are subject to change.
- This code is unaudited. Use at your own risk.
- I repeat. This is not ready for production.
If you'd like to install the latest dev release, grab the latest build.zip here and add it to your local chrome profile, using developer mode. See the video below.
setup.mp4
git clone [email protected]:coral-xyz/backpack.git
cd backpackGo to chrome://flags/#allow-insecure-localhost and enable the toggle, then restart chrome. Note: Please don't enable this if you don't know what you're doing. It will leave you vulnerable to exploits if left on. It is recommended to undo this step when you are done developing.
You can also optionally rename .env.example to .env and set your own variables.
yarn installyarn buildyarn startNote: In a fresh repo, you should run yarn build before yarn start.
If you run into issues with builds try running yarn clean and then start again.
Seeing `WebSocket connection to 'wss://localhost:9997/ws' failed` error messages in your console?
You need to install a SSL certificate for localhost as the one provided by webpack-dev-server is considered invalid. This step is optional as react-refresh will still function without it, but it's a good idea to try and fix this error because otherwise your browser will be making a lot of failed requests and webpack-dev-server might not be functioning to its full capabilities.
A relatively simple way of doing this is using mkcert
Instructions for how to install a trusted self-signed cert on macOS -
cd packages/app-extension
brew install mkcert
mkcert localhost
mkcert -install
Now the next time you run yarn start the errors should no longer appear.
Go to chrome://extensions, enable developer mode (top right) and drag the packages/app-extension/dev dir into the window. This version will have (Dev) in the title and supports live-reloading.
- Do you have a stale node process running? Try to kill it all:
killall -9 nodeand start over - Try running
yarn startfrom withinpackages/app-extensionwhile runningyarn startfrom root. This should work.
If you want to try the production build of the extension, run yarn build and drag the packages/app-extension/build dir into chrome://extensions as above. This version won't have hot-reloading and local plugins won't be visible unless you also run yarn start
Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion by you shall be licensed at the discretion of the repository maintainers without any additional terms or conditions.