chore(deps): update all non-major dependencies #420
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
^8.56.0
->^8.56.1
^18.19.3
->^18.19.5
^4.6.0
->^4.6.2
^13.6.1
->^13.6.2
^23.0.1
->^23.2.0
^3.3.5
->^3.3.7
^5.0.10
->^5.0.11
^1.1.0
->^1.1.3
^3.3.13
->^3.4.6
^1.8.26
->^1.8.27
Release Notes
cypress-io/cypress (cypress)
v13.6.2
Compare Source
Changelog: https://docs.cypress.io/guides/references/changelog#13-6-2
jsdom/jsdom (jsdom)
v23.2.0
Compare Source
This release switches our CSS selector engine from
nwsapi
to@asamuzakjp/dom-selector
. The new engine is more actively maintained, and supports many new selectors: see the package's documentation for the full list. It also works better with shadow trees.There is a potential of a performance regression due to this change. In our stress test benchmark, which runs most of these 273 selectors against this 128 KiB document, the new engine completes the benchmark only 0.25x as fast. However, we're hopeful that in more moderate usage this will not be a significant issue. Any help speeding up
@asamuzakjp/dom-selector
is appreciated, and feel free to open an issue if this has had a significant impact on your project.v23.1.0
Compare Source
ElementInternals
, including theshadowRoot
getter and the string-valued ARIA properties. (zjffun)Element
.history.pushState()
andhistory.replaceState()
to follow the latest specification, notably with regards to how they handle empty string inputs and what new URLs are possible.input.valueAsANumber
setter to handleNaN
correctly. (alexandertrefz)cssstyle
which contains several bug fixes.nightwatchjs/nightwatch (nightwatch)
v3.3.7
Compare Source
v3.3.6
Compare Source
vitejs/vite (vite)
v5.0.11
Compare Source
__vite__mapDeps
code before sourcemap file comment (#15483) (d2aa096), closes #15483,
inside base64 value ofsrcset
attribute (#15422) (8de7bd2), closes #15422vitest-dev/vitest (vitest)
v1.1.3
Compare Source
🐞 Bug Fixes
slowTestThreshold
to all reporters - by @hi-ogawa in https://github.com/vitest-dev/vitest/issues/4876 (1769c)View changes on GitHub
v1.1.2
Compare Source
🐞 Bug Fixes
expect(...).toMatchFileSnapshot()
matcher. - by @zmullett, Zac Mullett and @sheremet-va in https://github.com/vitest-dev/vitest/issues/4839 (b8140)memoryLimit
- by @inottn and @AriPerkkio in https://github.com/vitest-dev/vitest/issues/4802 (70e8a)View changes on GitHub
v1.1.1
Compare Source
🐞 Bug Fixes
inline: true
is set - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/4815 (8f622)--no-parallelism
- by @bonyuta0204 in https://github.com/vitest-dev/vitest/issues/4831 (5053a)skip
- by @hi-ogawa in https://github.com/vitest-dev/vitest/issues/4814 (19faf)beforeAll/afterAll
errors in junit reporter - by @hi-ogawa in https://github.com/vitest-dev/vitest/issues/4819 (2baea)View changes on GitHub
vuejs/core (vue)
v3.4.6
Compare Source
Bug Fixes
null
type for textarea value (#9997) (c379bc2), closes #9904v3.4.5
Compare Source
Bug Fixes
v3.4.4
Compare Source
Bug Fixes
watchEffect
(#9948) (f300a40)Performance Improvements
v3.4.3
Compare Source
Bug Fixes
v3.4.2
Compare Source
Bug Fixes
v3.4.1
Compare Source
Bug Fixes
Features
v3.4.0
Compare Source
Potential Actions Needed
To fully leverage new features in 3.4, it is recommended to also update the following dependencies when upgrading to 3.4:
If using TSX with Vue, check actions needed in Removed: Global JSX Namespace.
Make sure you are no longer using any deprecated features (if you are, you should have warnings in the console telling you so). They may have been removed in 3.4.
Features
once
option to watch (#9034) (a645e7a)using
syntax (#8786) (5b2bd1d)defineModel
support local mutation by default, remove local option (f74785b), closes /github.com/vuejs/rfcs/discussions/503#discussioncomment-7566278__VUE_PROD_HYDRATION_MISMATCH_DETAILS__
feature flag (#9550) (bc7698d)FunctionalComponent
(#8644) (927ab17)AriaAttributes
type (#8909) (fd0b6ba)ObjectPlugin
andFunctionPlugin
types (#8946) (fa4969e), closes #8577DefineProps
type (096ba81)PublicProps
type (#2403) (44135dc)h
with native elements (#9756) (a625376)ComponentInstance
type (#5408) (bfb8565)Performance Improvements
BREAKING CHANGES
Global JSX Registration Removed
Starting in 3.4, Vue no longer registers the global
JSX
namespace by default. This is necessary to avoid global namespace collision with React so that TSX of both libs can co-exist in the same project. This should not affect SFC-only users with latest version of Volar.If you are using TSX, there are two options:
Explicitly set jsxImportSource to
'vue'
intsconfig.json
before upgrading to 3.4. You can also opt-in per file by adding a/* @​jsxImportSource vue */
comment at the top of the file.If you have code that depends on the presence of the global
JSX
namespace, e.g. usage of types likeJSX.Element
etc., you can retain the exact pre-3.4 global behavior by explicitly referencingvue/jsx
, which registers the globalJSX
namespace.Note that this is a type-only breaking change in a minor release, which adheres to our release policy.
Deprecated Features Removed
app.config.unwrapInjectedRef
has been removed. It was deprecated and enabled by default in 3.3. In 3.4 it is no longer possible to disable this behavior.@vnodeXXX
event listeners in templates are now a compiler error instead of a deprecation warning. Use@vue:XXX
listeners instead.v-is
directive has been removed. It was deprecated in 3.3. Use theis
attribute withvue:
prefix instead.vuejs/language-tools (vue-tsc)
v1.8.27
Compare Source
JSX.Element
for compatible with vue 3.4 (https://github.com/vuejs/core/issues/9923)Configuration
📅 Schedule: Branch creation - "before 4am on Monday" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR has been generated by Mend Renovate. View repository job log here.