1
0
mirror of https://github.com/Unleash/unleash.git synced 2024-12-22 19:07:54 +01:00
unleash.unleash/frontend
dependabot[bot] 501071691c chore(deps): bump browserslist from 4.16.3 to 4.20.2 (#819)
Bumps [browserslist](https://github.com/browserslist/browserslist) from 4.16.3 to 4.20.2.
- [Release notes](https://github.com/browserslist/browserslist/releases)
- [Changelog](https://github.com/browserslist/browserslist/blob/main/CHANGELOG.md)
- [Commits](https://github.com/browserslist/browserslist/compare/4.16.3...4.20.2)

---
updated-dependencies:
- dependency-name: browserslist
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <support@github.com>

Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2022-03-28 11:58:50 +02:00
..
.github/workflows chore(deps): update actions/checkout action to v3 (#763) 2022-03-25 10:18:06 +01:00
cypress chore: update paths 🧼 (#820) 2022-03-28 09:49:59 +01:00
public
src chore: update paths 🧼 (#820) 2022-03-28 09:49:59 +01:00
.editorconfig
.gitignore
.nvmrc
.prettierignore
.prettierrc
CHANGELOG.md
cypress.json
index.js
LICENSE
package.json docs: Add some details on running and debugging the e2e tests (#526) 2022-03-25 12:13:39 +01:00
README.md docs: Add some details on running and debugging the e2e tests (#526) 2022-03-25 12:13:39 +01:00
renovate.json
tsconfig.json
typings.json
vercel.json
yarn.lock chore(deps): bump browserslist from 4.16.3 to 4.20.2 (#819) 2022-03-28 11:58:50 +02:00

unleash-frontend

This repo contains the Unleash Admin UI frontend app.

Run with a local instance of the unleash-api

First, start the unleash-api backend on port 4242. Then, start the unleash-frontend dev server:

cd ~/unleash-frontend
yarn install
yarn run start

Run with a heroku-hosted instance of unleash-api

Alternatively, instead of running unleash-api on localhost, use a remote instance:

cd ~/unleash-frontend
yarn install
yarn run start:heroku

Running end-to-end Tests

We have a set of Cypress tests that run on the build before a PR can be merged so it's important that you check these yourself before submitting a PR.

On the server the tests will run against the deployed Heroku app so this is what you probably want to test against:

yarn run start:heroku

In a different shell, you can run the tests themselves:

yarn run e2e:heroku

If you need to test against patches against a local server instance, you'll need to run that, and then run the end to end tests using:

yarn run e2e

You may also need to test that a feature works against the enterprise version of unleash. Assuming the Heroku instance is still running, this can be done by:

yarn run start:enterprise
yarn run e2e