a6a21bed46
* feat: add env specific serve commands where appropriate for apps * fix: typo in command call * feat: add custom executor for serving apps * chore: clean up project files and use the custom executor * chore: patch readmes * chore: split out logs into their own function * fix: prevent overriding env when no flag passed in * fix: add tsc to postinstall to take care of compiling the custom executors * fix: remove the custom serve executor from trading |
||
|---|---|---|
| .. | ||
| components | ||
| lib | ||
| pages | ||
| public | ||
| specs | ||
| .env | ||
| .env.devnet | ||
| .env.mainnet | ||
| .env.stagnet1 | ||
| .env.stagnet2 | ||
| .env.testnet | ||
| .eslintrc.json | ||
| client.graphql | ||
| index.d.ts | ||
| jest.config.js | ||
| next-env.d.ts | ||
| next.config.js | ||
| postcss.config.js | ||
| project.json | ||
| README.md | ||
| sentry.client.config.js | ||
| sentry.server.config.js | ||
| setup-tests.ts | ||
| tailwind.config.js | ||
| tsconfig.json | ||
| tsconfig.spec.json | ||
Trading
Development
First copy the configuration of the application you are starting:
cp .env.[environment] .env.local
Starting the app:
yarn nx serve explorer
Configuration
Example configurations are provided here:
There are a few different configuration options offered for this app:
| Flag | Purpose |
|---|---|
NX_VEGA_ENV |
The name of the currently connected vega environment |
NX_VEGA_URL |
The GraphQL query endpoint of a Vega data node |
NX_ETHEREUM_CHAIN_ID |
The ID of the Ethereum chain the currently connected Vega Network uses. E.g. Ropsten (3) for testnet |
NX_ETHEREUM_PROVIDER_URL |
The Ethereum Provider URL for getting data from the Ethereum network, for example Infura or a local node |
NX_ETHERSCAN_URL |
The Etherscan URL to link Ethereum transactions to |
Testing
To run the minimal set of unit tests, run the following:
yarn nx test trading
To run the UI automation tests with a mocked API, run:
yarn nx run trading-e2e:e2e