@shardeum-foundation/monitor-client v2.10.0

@shardeum-foundation/monitor-client

Releasing

If you're daring and want to cut and push a release to npm, you can do so solely by running npm run release. But I warn you - with great power, comes great responsibility ;)

How to run a custom monitor client branch (dev) with a local network.

1. go to the monitor client folder:

• run npm ci
• run npm link
• run npm run prepare

2. go to the monitor server folder:

• run npm ci
• run npm link @shardeum-foundation/monitor-client
• run npm run prepare

3. Go to your running (if running) shardeum-server folder

• shardus pm2 list // find the index of monitor server usually 1
• shardus pm2 stop // index usually 1

4. go to monitor server folder

• npm start

Running tests with puppeteer

Note: for right now it expects the monitor-server to be located at ../monitor-server, but you can set the MONITOR_SERVER_PATH environment variable to the path of your monitor-server.

1. npm run test:e2e

Troubleshooting e2e tests

On Mac OSX you may need to set PUPPETEER_EXECUTABLE_PATH="/Applications/Google Chrome.app/Contents/MacOS/Google Chrome" to avoid system security policies.