chore(deps): update all non-major dependencies #369
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:
^4.20231121.0
->^4.20231218.0
^6.3.1
->^6.4.1
^20.10.5
->^20.11.0
^1.25.2
->^1.28.0
^4.5.2
->^4.6.2
^3.3.12
->^3.4.10
^5.0.1
->^5.0.2
^1.9.0
->^1.10.0
^23.0.1
->^23.2.0
^1.5.5
->^1.5.6
^9.1.3
->^9.1.4
^1.4.1
->^1.6.1
^3.8.2
->^3.9.1
8.12.1
->8.14.1
^3.3.12
->^3.4.10
Release Notes
cloudflare/workerd (@cloudflare/workers-types)
v4.20231218.0
Compare Source
netlify/blobs (@netlify/blobs)
v6.4.1
Compare Source
Bug Fixes
v6.4.0
Compare Source
Features
connectLambda
method (#128) (d1061b4)Bug Fixes
EXDEV: cross-device link not permitted
(#132) (61b4ee6)upstash/upstash-redis (@upstash/redis)
v1.28.0
Compare Source
What's Changed
Full Changelog: upstash/redis-js@v1.27.1...v1.28.0
v1.27.1
Compare Source
What's Changed
Full Changelog: upstash/redis-js@v1.27.0...v1.27.1
v1.27.0
Compare Source
What's Changed
Full Changelog: upstash/redis-js@v1.26.0...v1.27.0
vuejs/core (@vue/compiler-sfc)
v3.4.10
Compare Source
Bug Fixes
v3.4.9
Compare Source
Bug Fixes
v3.4.8
Compare Source
Bug Fixes
v3.4.7
Compare Source
Bug Fixes
<template>
tags (#10034) (923d560)h
(#9991) (438a74a)Reverts
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.v3.3.13
Compare Source
Bug Fixes
dumbmatter/fakeIndexedDB (fake-indexeddb)
v5.0.2
Compare Source
IDBObjectStore.count
andIDBIndex.count
.unjs/h3 (h3)
v1.10.0
Compare Source
compare changes
🚀 Enhancements
data
(#594)🩹 Fixes
req.rawBody
beforereq.body
(#604)📖 Documentation
h3-compression
to community packages (#524)🌊 Types
isError
and updateDataT
default generic param (#582)🏡 Chore
🤖 CI
❤️ Contributors
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.unjs/listhen (listhen)
v1.5.6
Compare Source
compare changes
🩹 Fixes
localhost
in internalgenerateURL
util (6c76d31)📖 Documentation
🏡 Chore
❤️ Contributors
nodkz/mongodb-memory-server (mongodb-memory-server)
v9.1.4
Compare Source
Fixes
unjs/node-fetch-native (node-fetch-native)
v1.6.1
Compare Source
compare changes
📦 Build
❤️ Contributors
v1.6.0
Compare Source
compare changes
🚀 Enhancements
fetch
andcreateFetch
(#108)🩹 Fixes
❤️ Contributors
v1.5.1
Compare Source
compare changes
🩹 Fixes
📦 Build
/proxy
subpath export (584ee24)❤️ Contributors
v1.5.0
Compare Source
compare changes
🚀 Enhancements
🏡 Chore
❤️ Contributors
nuxt/nuxt (nuxt)
v3.9.1
Compare Source
✅ Upgrading
As usual, our recommendation for upgrading is to run:
This will refresh your lockfile as well, and ensures that you pull in updates from other dependencies that Nuxt relies on, particularly in the vue and unjs ecosystems.
👉 Changelog
compare changes
🔥 Performance
useRequestHeaders
(#24853)startsWith
to array access (#24744)🩹 Fixes
NuxtErrorBoundary
withssr: false
(#24896)any
in inferred injections (#25010)<ClientOnly>
(#25009)currentRoute
inRef
(#25026)💅 Refactors
nuxt-config-schema
(#25067)📖 Documentation
features
/future
docs (f5676fba5)vue-router
docs link (#24948)readValidatedBody
andgetValidatedQuery
(#24990)getValidatedRouterParams
(#25057)🏡 Chore
✅ Tests
❤️ Contributors
v3.9.0
Compare Source
👀 Highlights
A very merry Christmas to you and yours from all Nuxters involved in this release! 🎁🎄
We have lots of features packed into v3.9.0 and can't wait for you to try them out.
⚡️ Vite 5
This release comes with Vite 5 and Rollup 4 support. Module authors may need to check to ensure that any vite plugins you're creating are compatible with these latest releases.
This comes with a whole host of great improvements and bug fixes - check out the Vite changelog for more info.
✨ Vue 3.4 ready
This release is tested with the latest Vue 3.4 release candidate, and has the necessary configuration to take advantage of new features in Vue 3.4, including debugging hydration errors in production (just set
debug: true
) in your Nuxt config.👉 To take advantage, just update your
vue
version once v3.4 is released, or try out the release candidate today:🏝️ Interactive Server Components
This is a highly-experimental update, but it's now possible to play around with interactive components within Nuxt server components. You'll need to enable this new feature additionally to component islands:
Now, within a server component, you can specify components to hydrate by using the
nuxt-client
directive:We're pretty excited about this one - so do let us know how you're using it! 🙏
🔥 Automatic Server Optimisations
We now use Vite's new AST-aware 'define' to perform more accurate replacements on server-side code, meaning code like this will no longer throw an error:
This hasn't been possible until now because we haven't wanted to run the risk of accidentally replacing normal words like
document
within non-JS parts of your apps. But Vite's newdefine
functionality is powered byesbuild
and is syntax-aware, so we feel confident in enabling this functionality. Nevertheless, you can opt out if you need to:🚦 Granular Loading API
We now have a new hook-based system for
<NuxtLoadingIndicator>
, including auseLoadingIndicator
composable that lets you control/stop/start the loading state. You can also hook intopage:loading:start
andpage:loading:end
if you prefer.You can read more in the docs and in the original PR (#24010).
🏁 Run single events in
callOnce
Sometimes you only want to run code once, no matter how many times you load a page - and you don't want to run it again on the client if it ran on the server.
For this, we have a new utility:
callOnce
(#24787).Note that this utility is context-aware so it must be called in component setup function or Nuxt plugin, as with other Nuxt composables.
Read more in the docs.
🚨 Error Types
For a while now, errors returned by
useAsyncData
anduseFetch
have been typed pretty generically asError
. We've significantly improved the type possibilities for them to make them more accurate in terms of what you'll actually receive. (We normalise errors with theh3
createError
utility under the hood, so they can be serialised from server to client, for example.)We've tried to implement the type change in a backwards compatible way, but you might notice that you need to update the generic if you're manually configuring the generics for these composables. See (#24396) for more information, and do let us know if you experience any issues.
🔥 Schema Performance
We've taken some time in this release to make some minor performance improvements, so you should notice some things are a bit faster. This is an ongoing project and we have ideas for improving initial load time of the Nuxt dev server.
✅ Upgrading
As usual, our recommendation for upgrading is to run:
This will refresh your lockfile as well, and ensures that you pull in updates from other dependencies that Nuxt relies on, particularly in the unjs ecosystem.
👉 Changelog
compare changes
🚀 Enhancements
<NuxtLayout>
(#24116)addComponentsDir
(#24309)useCookie
([#24503](httConfiguration
📅 Schedule: Branch creation - "after 2am and before 3am" (UTC), Automerge - "after 1am and before 2am" (UTC).
🚦 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 if that's undesired.
This PR has been generated by Mend Renovate. View repository job log here.