5211bb763f
[](https://renovatebot.com) This PR contains the following updates: | Package | Change | Age | Adoption | Passing | Confidence | |---|---|---|---|---|---| | [sass](https://togithub.com/sass/dart-sass) | [`1.66.1` -> `1.68.0`](https://renovatebot.com/diffs/npm/sass/1.66.1/1.68.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 (sass)</summary> ### [`v1.68.0`](https://togithub.com/sass/dart-sass/blob/HEAD/CHANGELOG.md#1680) [Compare Source](https://togithub.com/sass/dart-sass/compare/1.67.0...1.68.0) - Fix the source spans associated with the `abs-percent` deprecation. ##### JS API - Non-filesystem importers can now set the `nonCanonicalScheme` field, which declares that one or more URL schemes (without `:`) will never be used for URLs returned by the `canonicalize()` method. - Add a `containingUrl` field to the `canonicalize()` and `findFileUrl()` methods of importers, which is set to the canonical URL of the stylesheet that contains the current load. For filesystem importers, this is always set; for other importers, it's set only if the current load has no URL scheme, or if its URL scheme is declared as non-canonical by the importer. ##### Dart API - Add `AsyncImporter.isNonCanonicalScheme`, which importers (async or sync) can use to indicate that a certain URL scheme will never be used for URLs returned by the `canonicalize()` method. - Add `AsyncImporter.containingUrl`, which is set during calls to the `canonicalize()` method to the canonical URL of the stylesheet that contains the current load. This is set only if the current load has no URL scheme, or if its URL scheme is declared as non-canonical by the importer. ##### Embedded Sass - The `CalculationValue.interpolation` field is deprecated and will be removed in a future version. It will no longer be set by the compiler, and if the host sets it it will be treated as equivalent to `CalculationValue.string` except that `"("` and `")"` will be added to the beginning and end of the string values. - Properly include TypeScript types in the `sass-embedded` package. ### [`v1.67.0`](https://togithub.com/sass/dart-sass/blob/HEAD/CHANGELOG.md#1670) [Compare Source](https://togithub.com/sass/dart-sass/compare/1.66.1...1.67.0) - All functions defined in CSS Values and Units 4 are now once again parsed as calculation objects: `round()`, `mod()`, `rem()`, `sin()`, `cos()`, `tan()`, `asin()`, `acos()`, `atan()`, `atan2()`, `pow()`, `sqrt()`, `hypot()`, `log()`, `exp()`, `abs()`, and `sign()`. Unlike in 1.65.0, function calls are *not* locked into being parsed as calculations or plain Sass functions at parse-time. This means that user-defined functions will take precedence over CSS calculations of the same name. Although the function names `calc()` and `clamp()` are still forbidden, users may continue to freely define functions whose names overlap with other CSS calculations (including `abs()`, `min()`, `max()`, and `round()` whose names overlap with global Sass functions). - **Breaking change**: As a consequence of the change in calculation parsing described above, calculation functions containing interpolation are now parsed more strictly than before. However, *almost* all interpolations that would have produced valid CSS will continue to work. The only exception is `#{$variable}%` which is not valid in Sass and is no longer valid in calculations. Instead of this, either use `$variable` directly and ensure it already has the `%` unit, or write `($variable * 1%)`. - **Potentially breaking bug fix**: The importer used to load a given file is no longer used to load absolute URLs that appear in that file. This was unintented behavior that contradicted the Sass specification. Absolute URLs will now correctly be loaded only from the global importer list. This applies to the modern JS API, the Dart API, and the embedded protocol. ##### Embedded Sass - Substantially improve the embedded compiler's performance when compiling many files or files that require many importer or function call round-trips with the embedded host. </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://developer.mend.io/github/Unleash/unleash). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzNy4wLjMiLCJ1cGRhdGVkSW5WZXIiOiIzNy4wLjMiLCJ0YXJnZXRCcmFuY2giOiJtYWluIn0=--> Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com> |
||
|---|---|---|
| .. | ||
| cypress | ||
| public | ||
| scripts | ||
| src | ||
| .editorconfig | ||
| .gitignore | ||
| .nvmrc | ||
| .prettierignore | ||
| .prettierrc | ||
| cypress.config.ts | ||
| cypress.d.ts | ||
| 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
Refer to the Contributing to Unleash guide for instructions. The frontend dev server runs (in port 3000) simultaneously with the backend dev server (in port 4242):
yarn install
yarn dev
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:
For now we only use generated types (src/openapi/models). We will use methods (src/openapi/apis) for new features soon.
yarn gen:api
rm -rf src/openapi/apis
clean up src/openapi/index.ts imports, only keep first line export * from './models';
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