mirror of
https://github.com/Unleash/unleash.git
synced 2024-12-22 19:07:54 +01:00
a309105553
[](https://renovatebot.com) This PR contains the following updates: | Package | Change | Age | Adoption | Passing | Confidence | |---|---|---|---|---|---| | [sass](https://togithub.com/sass/dart-sass) | [`1.58.3` -> `1.62.0`](https://renovatebot.com/diffs/npm/sass/1.58.3/1.62.0) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | --- ### Release Notes <details> <summary>sass/dart-sass</summary> ### [`v1.62.0`](https://togithub.com/sass/dart-sass/blob/HEAD/CHANGELOG.md#​1620) [Compare Source](https://togithub.com/sass/dart-sass/compare/1.61.0...1.62.0) - Deprecate the use of multiple `!global` or `!default` flags on the same variable. This deprecation is named `duplicate-var-flags`. - Allow special numbers like `var()` or `calc()` in the global functions: `grayscale()`, `invert()`, `saturate()`, and `opacity()`. These are also native CSS `filter` functions. This is in addition to number values which were already allowed. - Fix a cosmetic bug where an outer rule could be duplicated after nesting was resolved, instead of re-using a shared rule. ### [`v1.61.0`](https://togithub.com/sass/dart-sass/blob/HEAD/CHANGELOG.md#​1610) [Compare Source](https://togithub.com/sass/dart-sass/compare/1.60.0...1.61.0) - **Potentially breaking change:** Drop support for End-of-Life Node.js 12. - Fix remaining cases for the performance regression introduced in 1.59.0. ##### Embedded Sass - The JS embedded host now loads files from the working directory when using the legacy API. ### [`v1.60.0`](https://togithub.com/sass/dart-sass/blob/HEAD/CHANGELOG.md#​1600) [Compare Source](https://togithub.com/sass/dart-sass/compare/1.59.3...1.60.0) - Add support for the `pi`, `e`, `infinity`, `-infinity`, and `NaN` constants in calculations. These will be interpreted as the corresponding numbers. - Add support for unknown constants in calculations. These will be interpreted as unquoted strings. - Serialize numbers with value `infinity`, `-infinity`, and `NaN` to `calc()` expressions rather than CSS-invalid identifiers. Numbers with complex units still can't be serialized. ### [`v1.59.3`](https://togithub.com/sass/dart-sass/blob/HEAD/CHANGELOG.md#​1593) [Compare Source](https://togithub.com/sass/dart-sass/compare/1.59.2...1.59.3) - Fix a performance regression introduced in 1.59.0. - The NPM release of 1.59.0 dropped support for Node 12 without actually indicating so in its pubspec. This release temporarily adds back support so that the latest Sass version that declares it supports Node 12 actually does so. However, Node 12 is now end-of-life, so we will drop support for it properly in an upcoming release. ### [`v1.59.2`](https://togithub.com/sass/dart-sass/blob/HEAD/CHANGELOG.md#​1592) [Compare Source](https://togithub.com/sass/dart-sass/compare/1.59.1...1.59.2) - No user-visible changes. ### [`v1.59.1`](https://togithub.com/sass/dart-sass/blob/HEAD/CHANGELOG.md#​1591) [Compare Source](https://togithub.com/sass/dart-sass/compare/1.59.0...1.59.1) - No user-visible changes. ### [`v1.59.0`](https://togithub.com/sass/dart-sass/blob/HEAD/CHANGELOG.md#​1590) [Compare Source](https://togithub.com/sass/dart-sass/compare/1.58.3...1.59.0) ##### Command Line Interface - Added a new `--fatal-deprecation` flag that lets you treat a deprecation warning as an error. You can pass an individual deprecation ID (e.g. `slash-div`) or you can pass a Dart Sass version to treat all deprecations initially emitted in that version or earlier as errors. - New `--future-deprecation` flag that lets you opt into warning for use of certain features that will be deprecated in the future. At the moment, the only option is `--future-deprecation=import`, which will emit warnings for Sass `@import` rules, which are not yet deprecated, but will be in the future. ##### Dart API - New `Deprecation` enum, which contains the different current and future deprecations used by the new CLI flags. - The `compile` methods now take in `fatalDeprecations` and `futureDeprecations` parameters, which work similarly to the CLI flags. </details> --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Enabled. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Mend Renovate](https://www.mend.io/free-developer-tools/renovate/). View repository job log [here](https://app.renovatebot.com/dashboard#github/Unleash/unleash). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzNS41OC4wIiwidXBkYXRlZEluVmVyIjoiMzUuNTguMCJ9--> Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com> |
||
|---|---|---|
| .. | ||
| cypress | ||
| public | ||
| scripts | ||
| src | ||
| .editorconfig | ||
| .gitignore | ||
| .nvmrc | ||
| .prettierignore | ||
| .prettierrc | ||
| cypress.d.ts | ||
| cypress.json | ||
| index.html | ||
| index.js | ||
| orval.config.js | ||
| package.json | ||
| README.md | ||
| tsconfig.json | ||
| tsconfig.node.json | ||
| vercel.json | ||
| vite.config.ts | ||
| yarn.lock | ||
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