You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current documentation is not quite specific enough when a new dev is trying to get the project up and running locally, the instructions can be a bit arbitrary, not synchronised well enough and not specific enough.
To get a local version of the wallet running and to be able to run the E2E tests, the user needs to step through the following instructions:
After some conversation with @helciofranco, it would be a good idea to re-work the
Running Locally
section of thefuels-wallet
documentation https://wallet.fuel.network/docs/contributing/running-locally/The current documentation is not quite specific enough when a new dev is trying to get the project up and running locally, the instructions can be a bit arbitrary, not synchronised well enough and not specific enough.
To get a local version of the wallet running and to be able to run the E2E tests, the user needs to step through the following instructions:
pnpm install
pnpm exec playwright install --with-deps chromium
cp packages/app/.env.example packages/app/.env
(to setup our network)pnpm node:up
(to start a local fuel node)pnpm dev:crx
(to start the extension locally)At this point the prompt will not return but the user will see the following screen:
pnpm test:e2e
- at this point, all the tests should passIf other examples of commands are shown in the documentation, then be specific about what the command does.
For other
.env
example files, like,.env.tests
and.env.production
, let the user know what these examples are for and when they should be used.The text was updated successfully, but these errors were encountered: