Across frontend

Web UI for Across.

App: https://app.across.to
Docs: https://docs.across.to
Medium: https://medium.com/across-protocol

Development

Requirements

Local setup

Clone this repository, install deps and create an .env file by running:

yarn
cp .env.example .env

Adjust values in the created .env accordingly.

Start dev server

Start the frontend with a dev server by running:

PORT=3000 vercel dev

Build production bundle

yarn build

Run unit tests

yarn test

Run e2e tests

Our e2e tests use Playwright and Synpress. You can configure some custom env vars for running e2e tests by creating a file .env.e2e that might have the following content:

# This will default to http://127.0.0.1:3000 but can be overridden to target a different deployment
E2E_DAPP_URL=
# Seed phrase to use for MetaMask when running e2e tests
E2E_MM_SEED_PHRASE=
# Password to use for MetaMask when running e2e tests
E2E_MM_PASSWORD=
# Custom Infura project id to use when running e2e tests
E2E_INFURA_ID=

To run the tests locally, first make sure to have a local dev sever running:

PORT=3000 yarn dev

Make sure to setup the wallet cache by running

yarn synpress ./e2e/wallet-setup

If you want to start the Playwright UI run:

yarn test:e2e:headless:ui

If you want to run the tests from the CLI, run:

yarn test:e2e:headless

Pull Data from Amplitude

The src/ampli directory can be refreshed with new tracking data by running the following steps:

Run yarn ampli login to log in to Amplitude
Run yarn ampli pull web
1. If Amplitude requests to create a new project, let it generate a ampli.json file.

Contributing

Have a look at CONTRIBUTING to get more information on contributions and best practices.

License

across-protocol/frontend

About

Resources

License

Stars

Watchers

Forks

Releases

Packages 0

Contributors 23

Languages

Packages