1
0
mirror of https://github.com/Unleash/unleash.git synced 2024-12-22 19:07:54 +01:00
unleash.unleash/frontend
renovate[bot] aeb65d3cd4
chore(deps): update dependency sass to v1.63.4 (#4056)
[![Mend
Renovate](https://app.renovatebot.com/images/banner.svg)](https://renovatebot.com)

This PR contains the following updates:

| Package | Change | Age | Adoption | Passing | Confidence |
|---|---|---|---|---|---|
| [sass](https://togithub.com/sass/dart-sass) | [`1.62.1` ->
`1.63.4`](https://renovatebot.com/diffs/npm/sass/1.62.1/1.63.4) |
[![age](https://badges.renovateapi.com/packages/npm/sass/1.63.4/age-slim)](https://docs.renovatebot.com/merge-confidence/)
|
[![adoption](https://badges.renovateapi.com/packages/npm/sass/1.63.4/adoption-slim)](https://docs.renovatebot.com/merge-confidence/)
|
[![passing](https://badges.renovateapi.com/packages/npm/sass/1.63.4/compatibility-slim/1.62.1)](https://docs.renovatebot.com/merge-confidence/)
|
[![confidence](https://badges.renovateapi.com/packages/npm/sass/1.63.4/confidence-slim/1.62.1)](https://docs.renovatebot.com/merge-confidence/)
|

---

### Release Notes

<details>
<summary>sass/dart-sass</summary>

###
[`v1.63.4`](https://togithub.com/sass/dart-sass/blob/HEAD/CHANGELOG.md#&#8203;1634)

[Compare
Source](https://togithub.com/sass/dart-sass/compare/1.63.3...1.63.4)

##### JavaScript API

- Re-enable support for `import sass from 'sass'` when loading the
package from
an ESM module in Node.js. However, this syntax is now deprecated; ESM
users
    should use `import * as sass from 'sass'` instead.

On the browser and other ESM-only platforms, only `import * as sass from
    'sass'` is supported.

- Properly export the legacy API values `TRUE`, `FALSE`, `NULL`, and
`types` from
    the ECMAScript module API.

##### Embedded Sass

- Fix a race condition where closing standard input while requests are
in-flight
    could sometimes cause the process to hang rather than shutting down
    gracefully.

- Properly include the root stylesheet's URL in the set of loaded URLs
when it
    fails to parse.

###
[`v1.63.3`](https://togithub.com/sass/dart-sass/blob/HEAD/CHANGELOG.md#&#8203;1633)

[Compare
Source](https://togithub.com/sass/dart-sass/compare/1.63.2...1.63.3)

##### JavaScript API

-   Fix loading Sass as an ECMAScript module on Node.js.

###
[`v1.63.2`](https://togithub.com/sass/dart-sass/blob/HEAD/CHANGELOG.md#&#8203;1632)

[Compare
Source](https://togithub.com/sass/dart-sass/compare/1.63.1...1.63.2)

-   No user-visible changes.

###
[`v1.63.1`](https://togithub.com/sass/dart-sass/blob/HEAD/CHANGELOG.md#&#8203;1631)

[Compare
Source](https://togithub.com/sass/dart-sass/compare/1.63.0...1.63.1)

-   No user-visible changes.

###
[`v1.63.0`](https://togithub.com/sass/dart-sass/blob/HEAD/CHANGELOG.md#&#8203;1630)

[Compare
Source](https://togithub.com/sass/dart-sass/compare/1.62.1...1.63.0)

##### JavaScript API

- Dart Sass's JS API now supports running in the browser. Further
details and
instructions for use are in [the
README](README.md#dart-sass-in-the-browser).

##### Embedded Sass

- The Dart Sass embedded compiler is now included as part of the primary
Dart
Sass distribution, rather than a separate executable. To use the
embedded
compiler, just run `sass --embedded` from any Sass executable (other
than the
    pure JS executable).

The Node.js embedded host will still be distributed as the
`sass-embedded`
package on npm. The only change is that it will now provide direct
access to a
    `sass` executable with the same CLI as the `sass` package.

- The Dart Sass embedded compiler now uses version 2.0.0 of the Sass
embedded
protocol. See [the spec][embedded-protocol-spec] for a full description
of the
protocol, and [the changelog][embedded-protocol-changelog] for a summary
of
    changes since version 1.2.0.

[embedded-protocol-spec]:
https://togithub.com/sass/sass/blob/main/spec/embedded-protocol.md

[embedded-protocol-changelog]:
https://togithub.com/sass/sass/blob/main/EMBEDDED_PROTOCOL_CHANGELOG.md

- The Dart Sass embedded compiler now runs multiple simultaneous
compilations in
    parallel, rather than serially.

</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:eyJjcmVhdGVkSW5WZXIiOiIzNS4xMzEuMCIsInVwZGF0ZWRJblZlciI6IjM1LjEzMS4wIiwidGFyZ2V0QnJhbmNoIjoibWFpbiJ9-->

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
2023-06-23 18:29:02 +00:00
..
cypress
public
scripts
src feat: upgrade AdminAlert to PermissionGuard (#4074) 2023-06-23 13:25:35 +01:00
.editorconfig
.gitignore
.nvmrc
.prettierignore
.prettierrc
cypress.config.ts
cypress.d.ts
index.html
index.js
orval.config.js
package.json chore(deps): update dependency sass to v1.63.4 (#4056) 2023-06-23 18:29:02 +00:00
README.md
tsconfig.json
tsconfig.node.json
vercel.json
vite.config.ts
yarn.lock chore(deps): update dependency sass to v1.63.4 (#4056) 2023-06-23 18:29:02 +00:00

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:

./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