1
0
mirror of https://github.com/Unleash/unleash.git synced 2024-11-01 19:07:38 +01:00
unleash.unleash/frontend
2023-03-01 12:38:47 +00:00
..
cypress refactor: remove variants per environment feature flag (#3102) 2023-02-14 14:02:02 +00:00
public
src feat: add download and delete all buttons to sign-on log UI (#3231) 2023-03-01 12:38:47 +00:00
.editorconfig add editorconfig 2016-12-05 23:08:32 +01:00
.gitignore Feat/grouping fixes (#1146) 2022-07-25 10:14:02 +00:00
.nvmrc
.prettierignore
.prettierrc
cypress.json
index.html
index.js
orval.config.js
package.json chore(deps): update emotion monorepo to v11.10.6 (#3222) 2023-03-01 11:27:19 +00:00
README.md
tsconfig.json Add multiple tags (#3032) 2023-02-03 12:28:06 +02:00
tsconfig.node.json
vercel.json
vite.config.ts
yarn.lock chore(deps): update emotion monorepo to v11.10.6 (#3222) 2023-03-01 11:27:19 +00:00

frontend

This directory 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 frontend dev server:

cd ~/frontend
yarn install
yarn run start

Run with a sandbox instance of the Unleash API

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

cd ~/frontend
yarn install
yarn run start:sandbox

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:sandbox

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

Generating the OpenAPI client

The frontend uses an OpenAPI client generated from the backend's OpenAPI spec. Whenever there are changes to the backend API, the client should be regenerated:

./scripts/generate-openapi.sh

This script assumes that you have a running instance of the enterprise backend at http://localhost:4242. The new OpenAPI client will be generated from the runtime schema of this instance. The target URL can be changed by setting the UNLEASH_OPENAPI_URL env var.

Analyzing bundle size

npx vite-bundle-visualizer in the root of the frontend directory