2016-11-10 14:26:24 +01:00
{
2022-08-26 09:25:31 +02:00
"name" : "unleash-frontend-local" ,
"version" : "0.0.0" ,
"private" : true ,
2023-10-02 14:25:46 +02:00
"files" : [ "index.js" , "build" ] ,
2016-11-10 14:26:24 +01:00
"engines" : {
2023-04-18 14:42:49 +02:00
"node" : ">=18"
2016-11-10 14:26:24 +01:00
} ,
"scripts" : {
2022-08-30 10:52:30 +02:00
"build" : "vite build" ,
chore: simplify package scripts (#3736)
# Simplify package scripts
This PR's purpose is to raise a discussion surrounding our current
package scripts.
It includes some suggestions that aim to simplify the scripts and
hopefully bring a much more straightforward approach to developing and
contributing to Unleash.
Building (prod) should only happen **explicitly** and when needed.
## Before PR (current behavior)
- Clone the project;
- Open 2 terminals: One for `unleash` and another for
`unleash/frontend`;
- On `unleash`:
- Run `yarn` (which will also build, for some reason?);
- Run `yarn start:dev` to start backend in dev mode (`tsc-watch`);
- On `unleash/frontend`:
- Run `yarn` (which will also build, for some reason?);
- Run `yarn start` to start frontend in dev mode (`vite`);
So it seems to me like we build unnecessarily every time we install
dependencies. Neither dev scripts need to build the project, as backend
uses `tsc-watch` and frontend uses `vite`. I'm unsure why this is the
case, as building can take a very long time.
There's also some complexity in the way we need to split the terminal to
`cd` into `frontend` and treat it as a different project. The fact that
we have different script names is also confusing (`yarn start`, `yarn
start:dev`, etc).
## After PR
- Clone the project;
- Run `yarn` to install all dependencies;
- Run `yarn dev` to get started developing Unleash;
Running `yarn` should take care of everything needed to start
developing. This includes installing dependencies for frontend as well.
It should not build projects if we are not being explicit about it,
especially since we don't need to build them at this stage.
Running `yarn dev` should start the project in dev mode. This means
running both projects in `dev` mode, which for `backend` means running
`tsc-watch` and for `frontend` means running `vite`.
Here this PR attempts to provide a better DX by using
[concurrently](https://www.npmjs.com/package/concurrently) and
[wait-on](https://www.npmjs.com/package/wait-on) - This means both tasks
are ran simultaneously, stdout is labeled accordingly, and are stopped
together. It also means that `frontend` waits for `backend` to be
serving at `4242` before starting, since `frontend` starts pretty much
immediately with `vite` and `backend` takes a bit longer. Of course,
when the `backend` is hot-reloading you may still find some
`ECONNREFUSED`s on `frontend` stdout while it recompiles.
No more splitting your terminal and treating `frontend` as a separate
project.
## Discussion points
Maybe there's a better alternative to `tsc-watch`? I briefly explored
some alternatives and while they had a much faster starting speed,
hot-reload was sometimes slower. IMO we should aspire to run
`src/server-dev.ts` directly and only compile when needed.
Running `dev:backend` still serves a version of the frontend (at 4242).
**Why? Can we remove that behavior?**
I can't imagine a scenario in dev where we wouldn't want to run the
latest version of the frontend with `vite`.
~~**Note:** This PR removes all other out-of-scope scripts to focus on
this revamp. If we decide to merge it, we should evaluate what other
existing scripts we still want to include. May be a good opportunity to
clean up unused ones and only include the ones we really use. This
includes scripts that our GH actions rely on.~~
**Update:** In an effort to minimize impact surface of this PR and make
it a bit more ready for merging:
- It updates some docs in
https://github.com/Unleash/unleash/pull/3736/commits/2a4ff805e87b65d9c1256effaa189ddcccba15fb
and
https://github.com/Unleash/unleash/pull/3736/commits/1bbc4882519b5a82e3116f0be255ad24a6f3ce53
to reflect our new simplified flow;
- It includes the old package scripts for now in
https://github.com/Unleash/unleash/pull/3736/commits/039bc04699ac880e491fd3ce01f9bcd6f97a94b9;
- It updates some of our GH actions to reflect the new scripts in
https://github.com/Unleash/unleash/pull/3736/commits/7782cb9b12e37ee844507e41ef2b7137eaf55666;
Given its current status I'll promote the PR to "ready for review".
I still think we should have a second look at our existing scripts and
GH actions to see what we really need and/or should adapt, but it should
be a team effort so we have a broader context. Maybe on a follow-up PR.
Does this require any changes to related projects (e.g. Enterprise)?
---------
Co-authored-by: Gastón Fournier <gaston@getunleash.io>
2023-05-12 12:23:22 +02:00
"dev" : "vite" ,
2022-05-05 17:15:22 +02:00
"start" : "vite" ,
2022-12-16 19:09:24 +01:00
"start:prod" : "vite build && vite preview" ,
2022-10-19 14:02:00 +02:00
"start:sandbox" : "UNLEASH_API=https://sandbox.getunleash.io/ospro yarn run start" ,
2024-01-05 09:23:12 +01:00
"start:sandbox:enterprise" : "UNLEASH_API=https://sandbox.getunleash.io/ VITE_TEST_REDIRECT=true UNLEASH_BASE_PATH=/enterprise/ yarn run start" ,
2023-01-17 13:33:52 +01:00
"start:demo2" : "UNLEASH_API=https://sandbox.getunleash.io/ UNLEASH_BASE_PATH=/demo2/ yarn run start" ,
"start:enterprise" : "UNLEASH_API=https://unleash.herokuapp.com VITE_TEST_REDIRECT=true yarn run start" ,
2023-02-17 12:15:50 +01:00
"start:demo" : "UNLEASH_BASE_PATH=/demo/ UNLEASH_API=https://app.unleash-hosted.com/ yarn run start" ,
2023-11-17 11:42:32 +01:00
"test" : "NODE_OPTIONS=\"${NODE_OPTIONS} --no-experimental-fetch\" vitest run" ,
2023-04-18 10:35:32 +02:00
"test:snapshot" : "NODE_OPTIONS=\"${NODE_OPTIONS} --no-experimental-fetch\" yarn test -u" ,
2023-12-05 17:31:23 +01:00
"test:watch" : "NODE_OPTIONS=\"${NODE_OPTIONS} --no-experimental-fetch\" vitest watch" ,
2023-10-02 14:25:46 +02:00
"lint" : "biome lint src --apply" ,
2023-10-06 10:46:38 +02:00
"lint:check" : "biome check src" ,
2023-10-02 14:25:46 +02:00
"fmt" : "biome format src --write" ,
2023-10-06 10:46:38 +02:00
"fmt:check" : "biome check src" ,
2022-09-30 13:01:32 +02:00
"ts:check" : "tsc" ,
2023-04-18 10:35:32 +02:00
"e2e" : "NODE_OPTIONS=\"${NODE_OPTIONS} --no-experimental-fetch\" yarn run cypress open --config baseUrl='http://localhost:3000' --env AUTH_USER=admin,AUTH_PASSWORD=unleash4all" ,
2023-12-14 15:12:13 +01:00
"e2e:oss" : "yarn --cwd frontend run cypress run --spec \"cypress/oss/**/*.spec.ts\" --config baseUrl=\"http://localhost:${EXPOSED_PORT:-4242}\" --env AUTH_USER=admin,AUTH_PASSWORD=unleash4all" ,
2023-04-18 10:35:32 +02:00
"e2e:heroku" : "NODE_OPTIONS=\"${NODE_OPTIONS} --no-experimental-fetch\" yarn run cypress open --config baseUrl='https://unleash.herokuapp.com' --env AUTH_USER=admin,AUTH_PASSWORD=unleash4all" ,
"gen:api" : "NODE_OPTIONS=\"${NODE_OPTIONS} --no-experimental-fetch\" orval --config orval.config.js" ,
"gen:api:demo" : "NODE_OPTIONS=\"${NODE_OPTIONS} --no-experimental-fetch\" UNLEASH_OPENAPI_URL=https://app.unleash-hosted.com/demo/docs/openapi.json yarn run gen:api" ,
chore: simplify package scripts (#3736)
# Simplify package scripts
This PR's purpose is to raise a discussion surrounding our current
package scripts.
It includes some suggestions that aim to simplify the scripts and
hopefully bring a much more straightforward approach to developing and
contributing to Unleash.
Building (prod) should only happen **explicitly** and when needed.
## Before PR (current behavior)
- Clone the project;
- Open 2 terminals: One for `unleash` and another for
`unleash/frontend`;
- On `unleash`:
- Run `yarn` (which will also build, for some reason?);
- Run `yarn start:dev` to start backend in dev mode (`tsc-watch`);
- On `unleash/frontend`:
- Run `yarn` (which will also build, for some reason?);
- Run `yarn start` to start frontend in dev mode (`vite`);
So it seems to me like we build unnecessarily every time we install
dependencies. Neither dev scripts need to build the project, as backend
uses `tsc-watch` and frontend uses `vite`. I'm unsure why this is the
case, as building can take a very long time.
There's also some complexity in the way we need to split the terminal to
`cd` into `frontend` and treat it as a different project. The fact that
we have different script names is also confusing (`yarn start`, `yarn
start:dev`, etc).
## After PR
- Clone the project;
- Run `yarn` to install all dependencies;
- Run `yarn dev` to get started developing Unleash;
Running `yarn` should take care of everything needed to start
developing. This includes installing dependencies for frontend as well.
It should not build projects if we are not being explicit about it,
especially since we don't need to build them at this stage.
Running `yarn dev` should start the project in dev mode. This means
running both projects in `dev` mode, which for `backend` means running
`tsc-watch` and for `frontend` means running `vite`.
Here this PR attempts to provide a better DX by using
[concurrently](https://www.npmjs.com/package/concurrently) and
[wait-on](https://www.npmjs.com/package/wait-on) - This means both tasks
are ran simultaneously, stdout is labeled accordingly, and are stopped
together. It also means that `frontend` waits for `backend` to be
serving at `4242` before starting, since `frontend` starts pretty much
immediately with `vite` and `backend` takes a bit longer. Of course,
when the `backend` is hot-reloading you may still find some
`ECONNREFUSED`s on `frontend` stdout while it recompiles.
No more splitting your terminal and treating `frontend` as a separate
project.
## Discussion points
Maybe there's a better alternative to `tsc-watch`? I briefly explored
some alternatives and while they had a much faster starting speed,
hot-reload was sometimes slower. IMO we should aspire to run
`src/server-dev.ts` directly and only compile when needed.
Running `dev:backend` still serves a version of the frontend (at 4242).
**Why? Can we remove that behavior?**
I can't imagine a scenario in dev where we wouldn't want to run the
latest version of the frontend with `vite`.
~~**Note:** This PR removes all other out-of-scope scripts to focus on
this revamp. If we decide to merge it, we should evaluate what other
existing scripts we still want to include. May be a good opportunity to
clean up unused ones and only include the ones we really use. This
includes scripts that our GH actions rely on.~~
**Update:** In an effort to minimize impact surface of this PR and make
it a bit more ready for merging:
- It updates some docs in
https://github.com/Unleash/unleash/pull/3736/commits/2a4ff805e87b65d9c1256effaa189ddcccba15fb
and
https://github.com/Unleash/unleash/pull/3736/commits/1bbc4882519b5a82e3116f0be255ad24a6f3ce53
to reflect our new simplified flow;
- It includes the old package scripts for now in
https://github.com/Unleash/unleash/pull/3736/commits/039bc04699ac880e491fd3ce01f9bcd6f97a94b9;
- It updates some of our GH actions to reflect the new scripts in
https://github.com/Unleash/unleash/pull/3736/commits/7782cb9b12e37ee844507e41ef2b7137eaf55666;
Given its current status I'll promote the PR to "ready for review".
I still think we should have a second look at our existing scripts and
GH actions to see what we really need and/or should adapt, but it should
be a team effort so we have a broader context. Maybe on a follow-up PR.
Does this require any changes to related projects (e.g. Enterprise)?
---------
Co-authored-by: Gastón Fournier <gaston@getunleash.io>
2023-05-12 12:23:22 +02:00
"gen:api:sandbox" : "NODE_OPTIONS=\"${NODE_OPTIONS} --no-experimental-fetch\" UNLEASH_OPENAPI_URL=https://sandbox.getunleash.io/demo2/docs/openapi.json yarn run gen:api"
2016-11-10 14:26:24 +01:00
} ,
2021-04-09 13:38:30 +02:00
"devDependencies" : {
2024-01-12 10:25:59 +01:00
"@biomejs/biome" : "1.5.1" ,
2022-10-26 22:13:52 +02:00
"@codemirror/lang-json" : "6.0.1" ,
2024-01-04 19:16:44 +01:00
"@emotion/react" : "11.11.3" ,
2023-05-25 02:50:38 +02:00
"@emotion/styled" : "11.11.0" ,
chore(deps): update material-ui monorepo (#5862)
[](https://renovatebot.com)
This PR contains the following updates:
| Package | Change | Age | Adoption | Passing | Confidence |
|---|---|---|---|---|---|
| [@mui/icons-material](https://mui.com/material-ui/material-icons/)
([source](https://togithub.com/mui/material-ui/tree/HEAD/packages/mui-icons-material))
| [`5.15.2` ->
`5.15.3`](https://renovatebot.com/diffs/npm/@mui%2ficons-material/5.15.2/5.15.3)
|
[](https://docs.renovatebot.com/merge-confidence/)
|
[](https://docs.renovatebot.com/merge-confidence/)
|
[](https://docs.renovatebot.com/merge-confidence/)
|
[](https://docs.renovatebot.com/merge-confidence/)
|
| [@mui/lab](https://mui.com/material-ui/about-the-lab/)
([source](https://togithub.com/mui/material-ui/tree/HEAD/packages/mui-lab))
| [`5.0.0-alpha.158` ->
`5.0.0-alpha.159`](https://renovatebot.com/diffs/npm/@mui%2flab/5.0.0-alpha.158/5.0.0-alpha.159)
|
[](https://docs.renovatebot.com/merge-confidence/)
|
[](https://docs.renovatebot.com/merge-confidence/)
|
[](https://docs.renovatebot.com/merge-confidence/)
|
[](https://docs.renovatebot.com/merge-confidence/)
|
| [@mui/material](https://mui.com/material-ui/)
([source](https://togithub.com/mui/material-ui/tree/HEAD/packages/mui-material))
| [`5.15.2` ->
`5.15.3`](https://renovatebot.com/diffs/npm/@mui%2fmaterial/5.15.2/5.15.3)
|
[](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>mui/material-ui (@​mui/icons-material)</summary>
###
[`v5.15.3`](https://togithub.com/mui/material-ui/blob/HEAD/CHANGELOG.md#5153)
[Compare
Source](https://togithub.com/mui/material-ui/compare/v5.15.2...v5.15.3)
<!-- generated comparing v5.15.2..master -->
*Jan 3, 2024*
A big thanks to the 11 contributors who made this release possible.
This release was mostly about 🐛 bug fixes and 📚 documentation
improvements.
##### `@mui/material-nextjs@5.15.3`
- <!-- 06 -->\[material-nextjs] Fix order of emotion server
([#​40409](https://togithub.com/mui/material-ui/issues/40409))
[@​siriwatknp](https://togithub.com/siriwatknp)
##### `@mui/base@5.0.0-beta.30`
- <!-- 40 -->\[useSlider] Rearrange passive option in eventlisteners
([#​40235](https://togithub.com/mui/material-ui/issues/40235))
[@​Kamino0](https://togithub.com/Kamino0)
##### `@mui/lab@5.0.0-alpha.159`
- <!-- 14 -->Add use client directive
([#​40358](https://togithub.com/mui/material-ui/issues/40358))
[@​DiegoAndai](https://togithub.com/DiegoAndai)
##### `@mui/material-next@6.0.0-alpha.116`
- <!-- 13 -->\[List] Copy all List\* components to material-next
package
([#​40367](https://togithub.com/mui/material-ui/issues/40367))
[@​sai6855](https://togithub.com/sai6855)
- <!-- 12 -->Update CONTRIBUTING guide given v6/v7 rescheduling
([#​40363](https://togithub.com/mui/material-ui/issues/40363))
[@​DiegoAndai](https://togithub.com/DiegoAndai)
- <!-- 11 -->\[MenuItem] Fix spec import
([#​40271](https://togithub.com/mui/material-ui/issues/40271))
[@​DiegoAndai](https://togithub.com/DiegoAndai)
- <!-- 10 -->\[Option] Add Option component
([#​40270](https://togithub.com/mui/material-ui/issues/40270))
[@​DiegoAndai](https://togithub.com/DiegoAndai)
- <!-- 09 -->\[Slider] Replace lodash with internal utils
([#​40261](https://togithub.com/mui/material-ui/issues/40261))
[@​DiegoAndai](https://togithub.com/DiegoAndai)
- <!-- 08 -->\[Switch] Change files to TypeScript
([#​39894](https://togithub.com/mui/material-ui/issues/39894))
[@​lhilgert9](https://togithub.com/lhilgert9)
- <!-- 07 -->\[theme] Move ref palette out of color schemes
([#​40341](https://togithub.com/mui/material-ui/issues/40341))
[@​DiegoAndai](https://togithub.com/DiegoAndai)
##### Docs
- <!-- 41 -->\[base-ui] Polish the Table Pagination demos
([#​40281](https://togithub.com/mui/material-ui/issues/40281))
[@​danilo-leal](https://togithub.com/danilo-leal)
- <!-- 22 -->\[joy-ui] Fix dashboard template console errors
([#​40316](https://togithub.com/mui/material-ui/issues/40316))
[@​oliviertassinari](https://togithub.com/oliviertassinari)
- <!-- 21 -->\[joy-ui] Fix image size on the Files template
([#​40315](https://togithub.com/mui/material-ui/issues/40315))
[@​oliviertassinari](https://togithub.com/oliviertassinari)
- <!-- 20 -->\[material-ui] Revise the Divider page
([#​40356](https://togithub.com/mui/material-ui/issues/40356))
[@​danilo-leal](https://togithub.com/danilo-leal)
- <!-- 19 -->\[material-ui] Polish the Next.js integration page
([#​40317](https://togithub.com/mui/material-ui/issues/40317))
[@​oliviertassinari](https://togithub.com/oliviertassinari)
- <!-- 18 -->\[material-ui] Adding autoFocus on Virtual Popover
([#​40239](https://togithub.com/mui/material-ui/issues/40239))
[@​aacevski](https://togithub.com/aacevski)
- <!-- 17 -->\[material-ui] Revise the Roadmap page
([#​40054](https://togithub.com/mui/material-ui/issues/40054))
[@​danilo-leal](https://togithub.com/danilo-leal)
- <!-- 16 -->\[material-ui] Update the "showing and hiding" section on
the Tooltip page
([#​40283](https://togithub.com/mui/material-ui/issues/40283))
[@​anle9650](https://togithub.com/anle9650)
- <!-- 05 -->\[material-ui] Fix Slider's customized iOS demo to use
updated official colors
([#​39813](https://togithub.com/mui/material-ui/issues/39813))
[@​Super-Kenil](https://togithub.com/Super-Kenil)
- <!-- 15 -->\[examples] Simplify Next.js example
([#​40318](https://togithub.com/mui/material-ui/issues/40318))
[@​oliviertassinari](https://togithub.com/oliviertassinari)
##### Core
- <!-- 39 -->\[blog] Update open-graph cards for all posts
([#​40328](https://togithub.com/mui/material-ui/issues/40328))
[@​danilo-leal](https://togithub.com/danilo-leal)
- <!-- 38 -->\[blog] Correct git diff
[@​oliviertassinari](https://togithub.com/oliviertassinari)
- <!-- 37 -->\[code-infra] Update lerna and unpin its version
([#​40399](https://togithub.com/mui/material-ui/issues/40399))
[@​michaldudak](https://togithub.com/michaldudak)
- <!-- 36 -->\[code-infra] Break package dependency cycle between
[@​mui/material](https://togithub.com/mui/material) and
[@​mui/icons-material](https://togithub.com/mui/icons-material)
([#​40400](https://togithub.com/mui/material-ui/issues/40400))
[@​michaldudak](https://togithub.com/michaldudak)
- <!-- 35 -->\[code-infra] Break package dependency cycles
([#​40398](https://togithub.com/mui/material-ui/issues/40398))
[@​michaldudak](https://togithub.com/michaldudak)
- <!-- 34 -->\[code-infra] Sync bug issue template
([#​40305](https://togithub.com/mui/material-ui/issues/40305))
[@​oliviertassinari](https://togithub.com/oliviertassinari)
- <!-- 33 -->\[docs] Fix 301 link to Base UI
([#​40396](https://togithub.com/mui/material-ui/issues/40396))
[@​oliviertassinari](https://togithub.com/oliviertassinari)
- <!-- 32 -->\[docs] Link new MUI X components in sidnav
([#​40345](https://togithub.com/mui/material-ui/issues/40345))
[@​oliviertassinari](https://togithub.com/oliviertassinari)
- <!-- 31 -->\[docs] Fix 301 links to Toolpad
[@​oliviertassinari](https://togithub.com/oliviertassinari)
- <!-- 30 -->\[docs] Remove old notifications
[@​oliviertassinari](https://togithub.com/oliviertassinari)
- <!-- 29 -->\[docs] Always mention the npm tag with npx
([#​40335](https://togithub.com/mui/material-ui/issues/40335))
[@​oliviertassinari](https://togithub.com/oliviertassinari)
- <!-- 28 -->\[docs] Reduce network use on the All Components pages
([#​40313](https://togithub.com/mui/material-ui/issues/40313))
[@​oliviertassinari](https://togithub.com/oliviertassinari)
- <!-- 27 -->\[docs-infra] Fix missing button aria-label
([#​40394](https://togithub.com/mui/material-ui/issues/40394))
[@​oliviertassinari](https://togithub.com/oliviertassinari)
- <!-- 26 -->\[docs-infra] Fix a11y violation rule
([#​40393](https://togithub.com/mui/material-ui/issues/40393))
[@​oliviertassinari](https://togithub.com/oliviertassinari)
- <!-- 25 -->\[docs-infra] Prefetch pages on hover
([#​40314](https://togithub.com/mui/material-ui/issues/40314))
[@​oliviertassinari](https://togithub.com/oliviertassinari)
- <!-- 24 -->\[docs-infra] Fix footer links to link to the main domain
([#​40373](https://togithub.com/mui/material-ui/issues/40373))
[@​oliviertassinari](https://togithub.com/oliviertassinari)
- <!-- 23 -->\[docs-infra] Add stray design adjustments
([#​40347](https://togithub.com/mui/material-ui/issues/40347))
[@​danilo-leal](https://togithub.com/danilo-leal)
- <!-- 04 -->\[website] Fix Base UI page's component section imports &
styles
([#​40231](https://togithub.com/mui/material-ui/issues/40231))
[@​danilo-leal](https://togithub.com/danilo-leal)
- <!-- 03 -->\[website] Fix outdated Nhost image link
[@​oliviertassinari](https://togithub.com/oliviertassinari)
- <!-- 02 -->\[website] Shorten Joy UI description, 7 chars too long
[@​oliviertassinari](https://togithub.com/oliviertassinari)
- <!-- 01 -->\[website] Update some social preview images
([#​40282](https://togithub.com/mui/material-ui/issues/40282))
[@​danilo-leal](https://togithub.com/danilo-leal)
All contributors of this release in alphabetical order:
[@​aacevski](https://togithub.com/aacevski),
[@​anle9650](https://togithub.com/anle9650),
[@​danilo-leal](https://togithub.com/danilo-leal),
[@​DiegoAndai](https://togithub.com/DiegoAndai),
[@​Kamino0](https://togithub.com/Kamino0),
[@​lhilgert9](https://togithub.com/lhilgert9),
[@​michaldudak](https://togithub.com/michaldudak),
[@​oliviertassinari](https://togithub.com/oliviertassinari),
[@​sai6855](https://togithub.com/sai6855),
[@​siriwatknp](https://togithub.com/siriwatknp),
[@​Super-Kenil](https://togithub.com/Super-Kenil)
</details>
---
### Configuration
📅 **Schedule**: Branch creation - "after 7pm every weekday,before 5am
every weekday" in timezone Europe/Madrid, Automerge - At any time (no
schedule defined).
🚦 **Automerge**: Enabled.
♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the
rebase/retry checkbox.
👻 **Immortal**: This PR will be recreated if closed unmerged. Get
[config help](https://togithub.com/renovatebot/renovate/discussions) if
that's undesired.
---
- [ ] <!-- 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:eyJjcmVhdGVkSW5WZXIiOiIzNy4xMjcuMCIsInVwZGF0ZWRJblZlciI6IjM3LjEyNy4wIiwidGFyZ2V0QnJhbmNoIjoibWFpbiJ9-->
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
2024-01-11 20:50:58 +01:00
"@mui/icons-material" : "5.15.3" ,
"@mui/lab" : "5.0.0-alpha.159" ,
"@mui/material" : "5.15.3" ,
2023-12-08 09:07:57 +01:00
"@mui/x-date-pickers" : "^6.18.3" ,
2023-12-01 15:53:05 +01:00
"@tanstack/react-table" : "^8.10.7" ,
2023-06-24 06:24:24 +02:00
"@testing-library/dom" : "8.20.1" ,
2024-01-10 15:20:15 +01:00
"@testing-library/jest-dom" : "6.2.0" ,
2022-04-17 20:16:53 +02:00
"@testing-library/react" : "12.1.5" ,
2022-08-18 15:56:39 +02:00
"@testing-library/react-hooks" : "7.0.2" ,
2024-01-05 20:03:31 +01:00
"@testing-library/user-event" : "14.5.2" ,
2023-11-27 12:17:21 +01:00
"@types/debounce" : "1.2.4" ,
2023-11-27 13:23:23 +01:00
"@types/deep-diff" : "1.0.5" ,
2024-01-05 02:38:32 +01:00
"@types/jest" : "29.5.11" ,
2023-11-27 18:56:28 +01:00
"@types/lodash.clonedeep" : "4.5.9" ,
2023-12-01 15:53:05 +01:00
"@types/lodash.mapvalues" : "^4.6.9" ,
2023-11-28 00:03:23 +01:00
"@types/lodash.omit" : "4.5.9" ,
2024-01-16 19:34:39 +01:00
"@types/node" : "18.19.6" ,
2024-01-05 04:22:22 +01:00
"@types/react" : "17.0.74" ,
2023-11-29 10:24:30 +01:00
"@types/react-dom" : "17.0.25" ,
2023-11-28 13:53:10 +01:00
"@types/react-linkify" : "1.0.4" ,
2022-05-05 15:34:46 +02:00
"@types/react-router-dom" : "5.3.3" ,
2024-01-09 23:10:04 +01:00
"@types/react-table" : "7.7.19" ,
2023-11-29 03:17:22 +01:00
"@types/react-test-renderer" : "17.0.9" ,
2024-01-08 20:06:47 +01:00
"@types/react-timeago" : "4.1.7" ,
2023-11-28 15:47:16 +01:00
"@types/semver" : "7.5.6" ,
2023-01-27 09:13:57 +01:00
"@types/uuid" : "^9.0.0" ,
2023-12-04 20:36:21 +01:00
"@uiw/codemirror-theme-duotone" : "4.21.21" ,
2023-12-04 23:43:58 +01:00
"@uiw/react-codemirror" : "4.21.21" ,
2023-12-20 14:48:18 +01:00
"@vitejs/plugin-react" : "4.2.1" ,
2023-06-23 11:29:13 +02:00
"cartesian" : "^1.0.1" ,
2022-08-04 16:46:41 +02:00
"chart.js" : "3.9.1" ,
2022-12-28 14:09:19 +01:00
"chartjs-adapter-date-fns" : "3.0.0" ,
2024-01-10 23:09:18 +01:00
"classnames" : "2.5.1" ,
2022-11-14 17:27:49 +01:00
"copy-to-clipboard" : "3.3.3" ,
2023-04-18 11:56:15 +02:00
"countries-and-timezones" : "^3.4.0" ,
2024-01-09 02:02:38 +01:00
"cypress" : "13.6.2" ,
2023-05-08 10:16:18 +02:00
"cypress-vite" : "^1.4.0" ,
2023-05-16 16:45:53 +02:00
"date-fns" : "2.30.0" ,
2023-04-18 11:56:15 +02:00
"date-fns-tz" : "^2.0.0" ,
2024-01-17 09:29:17 +01:00
"debounce" : "2.0.0" ,
2021-11-08 16:02:06 +01:00
"deep-diff" : "1.0.2" ,
2022-10-10 12:18:37 +02:00
"dequal" : "2.0.3" ,
2022-03-24 20:06:59 +01:00
"fast-json-patch" : "3.1.1" ,
2022-04-29 01:07:23 +02:00
"http-proxy-middleware" : "2.0.6" ,
2023-04-03 17:42:06 +02:00
"immer" : "9.0.21" ,
2024-01-17 15:20:27 +01:00
"jsdom" : "23.1.0" ,
2021-09-27 09:12:17 +02:00
"lodash.clonedeep" : "4.5.0" ,
2023-12-01 15:53:05 +01:00
"lodash.mapvalues" : "^4.6.0" ,
2022-12-02 10:39:20 +01:00
"lodash.omit" : "4.5.0" ,
2022-12-16 15:12:36 +01:00
"mermaid" : "^9.3.0" ,
2023-07-20 16:15:45 +02:00
"millify" : "^6.0.0" ,
2023-02-12 17:25:43 +01:00
"msw" : "0.49.3" ,
2022-08-18 15:56:39 +02:00
"pkginfo" : "0.4.1" ,
2022-06-07 17:35:57 +02:00
"plausible-tracker" : "0.3.8" ,
2022-02-11 01:34:06 +01:00
"prop-types" : "15.8.1" ,
2021-09-27 09:12:17 +02:00
"react" : "17.0.2" ,
2022-08-02 05:44:13 +02:00
"react-chartjs-2" : "4.3.1" ,
2023-04-21 12:48:44 +02:00
"react-confetti" : "^6.1.0" ,
2021-09-27 09:12:17 +02:00
"react-dom" : "17.0.2" ,
2023-01-20 09:50:24 +01:00
"react-dropzone" : "14.2.3" ,
2022-10-10 12:18:37 +02:00
"react-error-boundary" : "3.1.4" ,
2022-12-10 18:26:53 +01:00
"react-hooks-global-state" : "2.1.0" ,
2023-04-18 11:56:15 +02:00
"react-joyride" : "^2.5.3" ,
"react-linkify" : "^1.0.0-alpha" ,
2023-04-21 12:48:44 +02:00
"react-markdown" : "^8.0.4" ,
chore(deps): update react-router monorepo to v6.21.1 (#5886)
[](https://renovatebot.com)
This PR contains the following updates:
| Package | Change | Age | Adoption | Passing | Confidence |
|---|---|---|---|---|---|
| [react-router](https://togithub.com/remix-run/react-router)
([source](https://togithub.com/remix-run/react-router/tree/HEAD/packages/react-router))
| [`6.20.1` ->
`6.21.1`](https://renovatebot.com/diffs/npm/react-router/6.20.1/6.21.1)
|
[](https://docs.renovatebot.com/merge-confidence/)
|
[](https://docs.renovatebot.com/merge-confidence/)
|
[](https://docs.renovatebot.com/merge-confidence/)
|
[](https://docs.renovatebot.com/merge-confidence/)
|
| [react-router-dom](https://togithub.com/remix-run/react-router)
([source](https://togithub.com/remix-run/react-router/tree/HEAD/packages/react-router-dom))
| [`6.20.1` ->
`6.21.1`](https://renovatebot.com/diffs/npm/react-router-dom/6.20.1/6.21.1)
|
[](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>remix-run/react-router (react-router)</summary>
###
[`v6.21.1`](https://togithub.com/remix-run/react-router/blob/HEAD/packages/react-router/CHANGELOG.md#6211)
[Compare
Source](https://togithub.com/remix-run/react-router/compare/react-router@6.21.0...react-router@6.21.1)
##### Patch Changes
- Fix bug with `route.lazy` not working correctly on initial SPA load
when `v7_partialHydration` is specified
([#​11121](https://togithub.com/remix-run/react-router/pull/11121))
- Updated dependencies:
- `@remix-run/router@1.14.1`
###
[`v6.21.0`](https://togithub.com/remix-run/react-router/blob/HEAD/packages/react-router/CHANGELOG.md#6210)
[Compare
Source](https://togithub.com/remix-run/react-router/compare/react-router@6.20.1...react-router@6.21.0)
##### Minor Changes
- Add a new `future.v7_relativeSplatPath` flag to implement a breaking
bug fix to relative routing when inside a splat route.
([#​11087](https://togithub.com/remix-run/react-router/pull/11087))
This fix was originally added in
[#​10983](https://togithub.com/remix-run/react-router/issues/10983)
and was later reverted in
[#​11078](https://togithub.com/remix-run/react-router/pull/11078)
because it was determined that a large number of existing applications
were relying on the buggy behavior (see
[#​11052](https://togithub.com/remix-run/react-router/issues/11052))
**The Bug**
The buggy behavior is that without this flag, the default behavior when
resolving relative paths is to *ignore* any splat (`*`) portion of the
current route path.
**The Background**
This decision was originally made thinking that it would make the
concept of nested different sections of your apps in `<Routes>` easier
if relative routing would *replace* the current splat:
```jsx
<BrowserRouter>
<Routes>
<Route path="/" element={<Home />} />
<Route path="dashboard/*" element={<Dashboard />} />
</Routes>
</BrowserRouter>
```
Any paths like `/dashboard`, `/dashboard/team`, `/dashboard/projects`
will match the `Dashboard` route. The dashboard component itself can
then render nested `<Routes>`:
```jsx
function Dashboard() {
return (
<div>
<h2>Dashboard</h2>
<nav>
<Link to="/">Dashboard Home</Link>
<Link to="team">Team</Link>
<Link to="projects">Projects</Link>
</nav>
<Routes>
<Route path="/" element={<DashboardHome />} />
<Route path="team" element={<DashboardTeam />} />
<Route path="projects" element={<DashboardProjects />} />
</Routes>
</div>
);
}
```
Now, all links and route paths are relative to the router above them.
This makes code splitting and compartmentalizing your app really easy.
You could render the `Dashboard` as its own independent app, or embed it
into your large app without making any changes to it.
**The Problem**
The problem is that this concept of ignoring part of a path breaks a lot
of other assumptions in React Router - namely that `"."` always means
the current location pathname for that route. When we ignore the splat
portion, we start getting invalid paths when using `"."`:
```jsx
// If we are on URL /dashboard/team, and we want to link to
/dashboard/team:
function DashboardTeam() {
// ❌ This is broken and results in <a href="/dashboard">
return <Link to=".">A broken link to the Current URL</Link>;
// ✅ This is fixed but super unintuitive since we're already at
/dashboard/team!
return <Link to="./team">A broken link to the Current URL</Link>;
}
```
We've also introduced an issue that we can no longer move our
`DashboardTeam` component around our route hierarchy easily - since it
behaves differently if we're underneath a non-splat route, such as
`/dashboard/:widget`. Now, our `"."` links will, properly point to
ourself *inclusive of the dynamic param value* so behavior will break
from it's corresponding usage in a `/dashboard/*` route.
Even worse, consider a nested splat route configuration:
```jsx
<BrowserRouter>
<Routes>
<Route path="dashboard">
<Route path="*" element={<Dashboard />} />
</Route>
</Routes>
</BrowserRouter>
```
Now, a `<Link to=".">` and a `<Link to="..">` inside the `Dashboard`
component go to the same place! That is definitely not correct!
Another common issue arose in Data Routers (and Remix) where any
`<Form>` should post to it's own route `action` if you the user doesn't
specify a form action:
```jsx
let router = createBrowserRouter({
path: "/dashboard",
children: [
{
path: "*",
action: dashboardAction,
Component() {
// ❌ This form is broken! It throws a 405 error when it submits because
// it tries to submit to /dashboard (without the splat value) and the
parent
// `/dashboard` route doesn't have an action
return <Form method="post">...</Form>;
},
},
],
});
```
This is just a compounded issue from the above because the default
location for a `Form` to submit to is itself (`"."`) - and if we ignore
the splat portion, that now resolves to the parent route.
**The Solution**
If you are leveraging this behavior, it's recommended to enable the
future flag, move your splat to it's own route, and leverage `../` for
any links to "sibling" pages:
```jsx
<BrowserRouter>
<Routes>
<Route path="dashboard">
<Route index path="*" element={<Dashboard />} />
</Route>
</Routes>
</BrowserRouter>
function Dashboard() {
return (
<div>
<h2>Dashboard</h2>
<nav>
<Link to="..">Dashboard Home</Link>
<Link to="../team">Team</Link>
<Link to="../projects">Projects</Link>
</nav>
<Routes>
<Route path="/" element={<DashboardHome />} />
<Route path="team" element={<DashboardTeam />} />
<Route path="projects" element={<DashboardProjects />} />
</Router>
</div>
);
}
```
This way, `.` means "the full current pathname for my route" in all
cases (including static, dynamic, and splat routes) and `..` always
means "my parents pathname".
##### Patch Changes
- Properly handle falsy error values in ErrorBoundary's
([#​11071](https://togithub.com/remix-run/react-router/pull/11071))
- Updated dependencies:
- `@remix-run/router@1.14.0`
</details>
<details>
<summary>remix-run/react-router (react-router-dom)</summary>
###
[`v6.21.1`](https://togithub.com/remix-run/react-router/blob/HEAD/packages/react-router-dom/CHANGELOG.md#6211)
[Compare
Source](https://togithub.com/remix-run/react-router/compare/react-router-dom@6.21.0...react-router-dom@6.21.1)
##### Patch Changes
- Updated dependencies:
- `react-router@6.21.1`
- `@remix-run/router@1.14.1`
###
[`v6.21.0`](https://togithub.com/remix-run/react-router/blob/HEAD/packages/react-router-dom/CHANGELOG.md#6210)
[Compare
Source](https://togithub.com/remix-run/react-router/compare/react-router-dom@6.20.1...react-router-dom@6.21.0)
##### Minor Changes
- Add a new `future.v7_relativeSplatPath` flag to implement a breaking
bug fix to relative routing when inside a splat route.
([#​11087](https://togithub.com/remix-run/react-router/pull/11087))
This fix was originally added in
[#​10983](https://togithub.com/remix-run/react-router/issues/10983)
and was later reverted in
[#​11078](https://togithub.com/remix-run/react-router/pull/11078)
because it was determined that a large number of existing applications
were relying on the buggy behavior (see
[#​11052](https://togithub.com/remix-run/react-router/issues/11052))
**The Bug**
The buggy behavior is that without this flag, the default behavior when
resolving relative paths is to *ignore* any splat (`*`) portion of the
current route path.
**The Background**
This decision was originally made thinking that it would make the
concept of nested different sections of your apps in `<Routes>` easier
if relative routing would *replace* the current splat:
```jsx
<BrowserRouter>
<Routes>
<Route path="/" element={<Home />} />
<Route path="dashboard/*" element={<Dashboard />} />
</Routes>
</BrowserRouter>
```
Any paths like `/dashboard`, `/dashboard/team`, `/dashboard/projects`
will match the `Dashboard` route. The dashboard component itself can
then render nested `<Routes>`:
```jsx
function Dashboard() {
return (
<div>
<h2>Dashboard</h2>
<nav>
<Link to="/">Dashboard Home</Link>
<Link to="team">Team</Link>
<Link to="projects">Projects</Link>
</nav>
<Routes>
<Route path="/" element={<DashboardHome />} />
<Route path="team" element={<DashboardTeam />} />
<Route path="projects" element={<DashboardProjects />} />
</Routes>
</div>
);
}
```
Now, all links and route paths are relative to the router above them.
This makes code splitting and compartmentalizing your app really easy.
You could render the `Dashboard` as its own independent app, or embed it
into your large app without making any changes to it.
**The Problem**
The problem is that this concept of ignoring part of a path breaks a lot
of other assumptions in React Router - namely that `"."` always means
the current location pathname for that route. When we ignore the splat
portion, we start getting invalid paths when using `"."`:
```jsx
// If we are on URL /dashboard/team, and we want to link to
/dashboard/team:
function DashboardTeam() {
// ❌ This is broken and results in <a href="/dashboard">
return <Link to=".">A broken link to the Current URL</Link>;
// ✅ This is fixed but super unintuitive since we're already at
/dashboard/team!
return <Link to="./team">A broken link to the Current URL</Link>;
}
```
We've also introduced an issue that we can no longer move our
`DashboardTeam` component around our route hierarchy easily - since it
behaves differently if we're underneath a non-splat route, such as
`/dashboard/:widget`. Now, our `"."` links will, properly point to
ourself *inclusive of the dynamic param value* so behavior will break
from it's corresponding usage in a `/dashboard/*` route.
Even worse, consider a nested splat route configuration:
```jsx
<BrowserRouter>
<Routes>
<Route path="dashboard">
<Route path="*" element={<Dashboard />} />
</Route>
</Routes>
</BrowserRouter>
```
Now, a `<Link to=".">` and a `<Link to="..">` inside the `Dashboard`
component go to the same place! That is definitely not correct!
Another common issue arose in Data Routers (and Remix) where any
`<Form>` should post to it's own route `action` if you the user doesn't
specify a form action:
```jsx
let router = createBrowserRouter({
path: "/dashboard",
children: [
{
path: "*",
action: dashboardAction,
Component() {
// ❌ This form is broken! It throws a 405 error when it submits because
// it tries to submit to /dashboard (without the splat value) and the
parent
// `/dashboard` route doesn't have an action
return <Form method="post">...</Form>;
},
},
],
});
```
This is just a compounded issue from the above because the default
location for a `Form` to submit to is itself (`"."`) - and if we ignore
the splat portion, that now resolves to the parent route.
**The Solution**
If you are leveraging this behavior, it's recommended to enable the
future flag, move your splat to it's own route, and leverage `../` for
any links to "sibling" pages:
```jsx
<BrowserRouter>
<Routes>
<Route path="dashboard">
<Route index path="*" element={<Dashboard />} />
</Route>
</Routes>
</BrowserRouter>
function Dashboard() {
return (
<div>
<h2>Dashboard</h2>
<nav>
<Link to="..">Dashboard Home</Link>
<Link to="../team">Team</Link>
<Link to="../projects">Projects</Link>
</nav>
<Routes>
<Route path="/" element={<DashboardHome />} />
<Route path="team" element={<DashboardTeam />} />
<Route path="projects" element={<DashboardProjects />} />
</Router>
</div>
);
}
```
This way, `.` means "the full current pathname for my route" in all
cases (including static, dynamic, and splat routes) and `..` always
means "my parents pathname".
##### Patch Changes
- Updated dependencies:
- `@remix-run/router@1.14.0`
- `react-router@6.21.0`
</details>
---
### Configuration
📅 **Schedule**: Branch creation - "after 7pm every weekday,before 5am
every weekday" in timezone Europe/Madrid, 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 these
updates 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:eyJjcmVhdGVkSW5WZXIiOiIzNy4xMjcuMCIsInVwZGF0ZWRJblZlciI6IjM3LjEyNy4wIiwidGFyZ2V0QnJhbmNoIjoibWFpbiJ9-->
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
2024-01-12 23:46:33 +01:00
"react-router-dom" : "6.21.1" ,
2022-05-17 16:33:12 +02:00
"react-table" : "7.8.0" ,
2022-02-25 10:55:39 +01:00
"react-test-renderer" : "17.0.2" ,
2023-09-14 22:29:13 +02:00
"react-timeago" : "7.2.0" ,
2024-01-10 03:12:06 +01:00
"sass" : "1.69.7" ,
2023-07-20 20:54:00 +02:00
"semver" : "7.5.4" ,
2023-10-06 08:59:26 +02:00
"swr" : "2.2.4" ,
2023-10-30 15:19:10 +01:00
"tss-react" : "4.9.3" ,
2022-10-07 19:54:29 +02:00
"typescript" : "4.8.4" ,
2023-12-01 15:53:05 +01:00
"use-query-params" : "^2.2.1" ,
chore(deps): update dependency vanilla-jsoneditor to ^0.21.0 (#5869)
[](https://renovatebot.com)
This PR contains the following updates:
| Package | Change | Age | Adoption | Passing | Confidence |
|---|---|---|---|---|---|
| [vanilla-jsoneditor](https://togithub.com/josdejong/svelte-jsoneditor)
| [`^0.19.0` ->
`^0.21.0`](https://renovatebot.com/diffs/npm/vanilla-jsoneditor/0.19.0/0.21.1)
|
[](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>josdejong/svelte-jsoneditor (vanilla-jsoneditor)</summary>
###
[`v0.21.1`](https://togithub.com/josdejong/svelte-jsoneditor/blob/HEAD/CHANGELOG.md#0211-2023-12-20)
[Compare
Source](https://togithub.com/josdejong/svelte-jsoneditor/compare/v0.21.0...v0.21.1)
###
[`v0.21.0`](https://togithub.com/josdejong/svelte-jsoneditor/blob/HEAD/CHANGELOG.md#0210-2023-12-20)
[Compare
Source](https://togithub.com/josdejong/svelte-jsoneditor/compare/v0.20.0...v0.21.0)
##### ⚠ BREAKING CHANGES
- The type `Content` is changed from `{ json: JSONValue} | { text:
string }` into
`{ json: unknown } | { text: string }`, and all other types having
`JSONValue` changed
to `unknown`. The return type of `JSONParser.stringify` changed from
`string` to
`string | undefined`.
##### Features
- change the type of `json` from `JSONValue` to `unknown`
([#​371](https://togithub.com/josdejong/svelte-jsoneditor/issues/371))
([dc4671a](https://togithub.com/josdejong/svelte-jsoneditor/commit/dc4671abaad7b2e8171caeffdbd83df157bf0196))
- implement `onRenderContextMenu` (fix
[#​82](https://togithub.com/josdejong/svelte-jsoneditor/issues/82))
([e53a620](https://togithub.com/josdejong/svelte-jsoneditor/commit/e53a620b6babf5f0cc58a432d4ac89861e6b267f))
- upgrade to upgrade `@sveltejs/kit@2`, `vite-plugin-svelte@3`,
`vite@5`, and `vitest@1`
([#​374](https://togithub.com/josdejong/svelte-jsoneditor/issues/374))
([b83e321](https://togithub.com/josdejong/svelte-jsoneditor/commit/b83e3214f8b4873f28247e0ee58a1f0c118d29f3))
###
[`v0.20.0`](https://togithub.com/josdejong/svelte-jsoneditor/blob/HEAD/CHANGELOG.md#0200-2023-12-06)
[Compare
Source](https://togithub.com/josdejong/svelte-jsoneditor/compare/v0.19.0...v0.20.0)
##### ⚠ BREAKING CHANGES
- When using `vanilla-jsoneditor` directly in the browser, you now have
to `import { JSONEditor } from 'vanilla-jsoneditor/standalone.js'`
instead of `import { JSONEditor } from 'vanilla-jsoneditor'`. For
projects with a build setup (React, Vue, Angular) it should be a drop-in
replacement.
- CSS variables are no longer defined globally, and the file
`themes/jse-theme-default.css` is now removed (replaced by an internal
`defaults.scss`). The provided dark theme still works as-is. The CSS
variable `--jse-modal-theme-color` has been renamed to
`--jse-modal-editor-theme-color`, and
`--jse-modal-theme-color-highlight` has been renamed to
`--jse-modal-editor-theme-color-highlight`.
##### Features
- export one bundle with and one without external dependencies in
`vanilla-jsoneditor`
([#​353](https://togithub.com/josdejong/svelte-jsoneditor/issues/353))
([9c1ad15](https://togithub.com/josdejong/svelte-jsoneditor/commit/9c1ad157a45f10d03fcc17f94ef0e82a66b5313e))
- update dependencies `codemirror`, `fontawesome`, `svelte-awesome`, and
dev dependencies
([75596ae](https://togithub.com/josdejong/svelte-jsoneditor/commit/75596ae2639df022a6fb0954ca517450e6c50f4c))
- use SCSS variables internally
([#​344](https://togithub.com/josdejong/svelte-jsoneditor/issues/344))
([ec4b788](https://togithub.com/josdejong/svelte-jsoneditor/commit/ec4b788e493b3ea0acc787687a63b4ff4b987024))
##### Bug Fixes
- allow `isEditing` property to be true when in `readOnly` mode (see
[#​342](https://togithub.com/josdejong/svelte-jsoneditor/issues/342))
([3b0bdb7](https://togithub.com/josdejong/svelte-jsoneditor/commit/3b0bdb7d40a4814c2f9498c4a9607d639071745b))
- cleanup a console.log
([005f189](https://togithub.com/josdejong/svelte-jsoneditor/commit/005f1896d8d05772435194c8d80bdf1244edf249))
- make argument `element` of helper function `onEscape` optional
([6eb9b82](https://togithub.com/josdejong/svelte-jsoneditor/commit/6eb9b823cdace19b5d389f8fdf8fb09db21874b0))
- styling issue with a button text color in dark mode
([4ff40f9](https://togithub.com/josdejong/svelte-jsoneditor/commit/4ff40f97d4726a8afbdb736601b866ab5500af61))
</details>
---
### Configuration
📅 **Schedule**: Branch creation - "after 7pm every weekday,before 5am
every weekday" in timezone Europe/Madrid, 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:eyJjcmVhdGVkSW5WZXIiOiIzNy4xMjcuMCIsInVwZGF0ZWRJblZlciI6IjM3LjEyNy4wIiwidGFyZ2V0QnJhbmNoIjoibWFpbiJ9-->
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
2024-01-12 03:27:37 +01:00
"vanilla-jsoneditor" : "^0.21.0" ,
chore(deps): update dependency vite to v5.0.11 (#5883)
[](https://renovatebot.com)
This PR contains the following updates:
| Package | Change | Age | Adoption | Passing | Confidence |
|---|---|---|---|---|---|
| [vite](https://vitejs.dev)
([source](https://togithub.com/vitejs/vite/tree/HEAD/packages/vite)) |
[`5.0.10` ->
`5.0.11`](https://renovatebot.com/diffs/npm/vite/5.0.10/5.0.11) |
[](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>vitejs/vite (vite)</summary>
###
[`v5.0.11`](https://togithub.com/vitejs/vite/blob/HEAD/packages/vite/CHANGELOG.md#small5011-2024-01-05-small)
[Compare
Source](https://togithub.com/vitejs/vite/compare/v5.0.10...v5.0.11)
- fix: don't pretransform classic script links
([#​15361](https://togithub.com/vitejs/vite/issues/15361))
([19e3c9a](https://togithub.com/vitejs/vite/commit/19e3c9a)), closes
[#​15361](https://togithub.com/vitejs/vite/issues/15361)
- fix: inject `__vite__mapDeps` code before sourcemap file comment
([#​15483](https://togithub.com/vitejs/vite/issues/15483))
([d2aa096](https://togithub.com/vitejs/vite/commit/d2aa096)), closes
[#​15483](https://togithub.com/vitejs/vite/issues/15483)
- fix(assets): avoid splitting `,` inside base64 value of `srcset`
attribute
([#​15422](https://togithub.com/vitejs/vite/issues/15422))
([8de7bd2](https://togithub.com/vitejs/vite/commit/8de7bd2)), closes
[#​15422](https://togithub.com/vitejs/vite/issues/15422)
- fix(html): handle offset magic-string slice error
([#​15435](https://togithub.com/vitejs/vite/issues/15435))
([5ea9edb](https://togithub.com/vitejs/vite/commit/5ea9edb)), closes
[#​15435](https://togithub.com/vitejs/vite/issues/15435)
- chore(deps): update dependency strip-literal to v2
([#​15475](https://togithub.com/vitejs/vite/issues/15475))
([49d21fe](https://togithub.com/vitejs/vite/commit/49d21fe)), closes
[#​15475](https://togithub.com/vitejs/vite/issues/15475)
- chore(deps): update tj-actions/changed-files action to v41
([#​15476](https://togithub.com/vitejs/vite/issues/15476))
([2a540ee](https://togithub.com/vitejs/vite/commit/2a540ee)), closes
[#​15476](https://togithub.com/vitejs/vite/issues/15476)
</details>
---
### Configuration
📅 **Schedule**: Branch creation - "after 7pm every weekday,before 5am
every weekday" in timezone Europe/Madrid, 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:eyJjcmVhdGVkSW5WZXIiOiIzNy4xMjcuMCIsInVwZGF0ZWRJblZlciI6IjM3LjEyNy4wIiwidGFyZ2V0QnJhbmNoIjoibWFpbiJ9-->
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
2024-01-12 21:44:45 +01:00
"vite" : "5.0.11" ,
2023-12-20 14:48:18 +01:00
"vite-plugin-env-compatible" : "2.0.1" ,
2023-10-01 02:51:52 +02:00
"vite-plugin-svgr" : "3.3.0" ,
2024-01-09 23:10:34 +01:00
"vite-tsconfig-paths" : "4.2.3" ,
2024-01-12 21:45:14 +01:00
"vitest" : "1.1.3" ,
2024-01-10 04:23:31 +01:00
"whatwg-fetch" : "3.6.20"
2017-02-23 22:18:23 +01:00
} ,
2023-01-05 11:57:53 +01:00
"optionalDependencies" : {
2023-07-20 12:59:55 +02:00
"orval" : "^6.17.0"
2023-01-05 11:57:53 +01:00
} ,
2022-10-14 11:44:59 +02:00
"resolutions" : {
2024-01-10 20:52:55 +01:00
"@codemirror/state" : "6.4.0" ,
2023-01-12 10:09:59 +01:00
"@xmldom/xmldom" : "^0.8.4" ,
2023-01-17 13:33:52 +01:00
"json5" : "^2.2.2" ,
2024-01-05 04:22:22 +01:00
"@types/react" : "17.0.74" ,
2023-11-29 10:24:30 +01:00
"@types/react-dom" : "17.0.25" ,
2023-07-20 20:54:00 +02:00
"semver" : "7.5.4"
2022-10-14 11:44:59 +02:00
} ,
2017-02-23 22:18:23 +01:00
"jest" : {
"moduleNameMapper" : {
2022-02-04 11:32:02 +01:00
"\\.(jpg|jpeg|png|gif|eot|otf|webp|ttf|woff|woff2|mp4|webm|wav|mp3|m4a|aac|oga)$" : "<rootDir>/src/__mocks__/fileMock.js" ,
"\\.svg" : "<rootDir>/src/__mocks__/svgMock.js" ,
2017-02-23 22:18:23 +01:00
"\\.(css|scss)$" : "identity-obj-proxy"
2022-02-04 11:32:02 +01:00
}
2021-04-07 09:04:48 +02:00
} ,
"browserslist" : {
2023-10-02 14:25:46 +02:00
"production" : [ ">0.2%" , "not dead" , "not op_mini all" ] ,
2021-04-07 09:04:48 +02:00
"development" : [
"last 1 chrome version" ,
"last 1 firefox version" ,
"last 1 safari version"
2021-02-05 14:33:32 +01:00
]
2023-12-08 09:07:57 +01:00
}
2016-11-10 14:26:24 +01:00
}
