fix(deps): update dependency nuxt to v3 #21
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:
^2.17.1
->^3.0.0
Release Notes
nuxt/nuxt (nuxt)
v3.14.0
Compare Source
v3.13.2
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 unjs ecosystem.
👉 Changelog
compare changes
🔥 Performance
🩹 Fixes
propsDestructure
by default (#28830)route
has enumerable keys (#28841)asyncData
(#28842)ssr: false
(#28834)injectAtEnd
to reduce circular auto-imports (#28822)buildDir
for unimport (#28899)<NuxtErrorBoundary>
(#28901)modules
array (#28922)filePath
(#28925)runWithContext
generic (#28926)inheritAttrs: false
for fragment components (#28939)<script>
blocks (4fd24381c)isNuxtMajorVersion
export (#29016)useError
(#28996)💅 Refactors
vite:preloadError
event (#28862)📖 Documentation
useFetch
parameter signature (#28993)🏡 Chore
noUncheckedSideEffectImports
(#28903)pending triage
to blank issues (#28923)htmlnano
+ pin workflow deps (#28946)✅ Tests
route
in template (#28967)🤖 CI
❤️ Contributors
v3.13.1
Compare Source
👀 Highlights
Although this is a patch release, there are two features I'd love to draw your attention to.
useId
now uses a built-in Vue composable for stable ids between server + client! https://github.com/nuxt/nuxt/pull/28285experimental.buildCache
feature now allows for quicker app rebuilds https://github.com/nuxt/nuxt/pull/28726As always, feedback is appreciated 🙏 ❤️
✅ 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
🔥 Performance
ServerPlaceholder
for ssr client components (#28563)🩹 Fixes
serverDir
relative to root (#28700)MiddlewareKey
(#28676)NuxtLink
(#28738)NuxtOptions
as well as config (#28747)CookieStore
events (#28760)appConfig
with non-iterable objects (#28773)isNuxtError
type inference (#28814)💅 Refactors
useId
(#28285)📖 Documentation
query
returned value fromuseRoute()
(#28743)--frozen-lockfile
when installing dependencies (#28794)🏡 Chore
tinyexec
internally (#28684)tinyglobby
internally (#28686)✅ Tests
❤️ Contributors
v3.13.0
Compare Source
👀 Highlights
I'm pretty excited about this release - we've ported some features we had planned for Nuxt v4 back to v3, as well as a raft of bug fixes and performance improvements - as usual.
Here are a few of things I'm most excited about.
🏘️ Route Groups
We now support naming directories with parentheses/brackets to organise your routes without affecting the path.
For example:
This will produce
/
,/about
and/contact
pages in your app. Themarketing
group is ignored for purposes of your URL structure.Read more in the original PR.
🏝️ Islands and Head Metadata
It's now possible for server component islands to manipulate the head, such as by adding SEO metadata when rendering.
Read more in #27987.
🪝 Custom Prefetch Triggers
We now support custom prefetch triggers for
NuxtLink
(#27846).For example:
It's also possible to enable/disable these globally for your app and override them per link.
For example:
🗺️ Better Server Source Maps
When running with
node --enable-source-maps
, you may have noticed that the source maps for the Vue files in your server build pointed to the Vite build output (something like.nuxt/dist/server/_nuxt/index-O15BBwZ3.js
).Now, even after your Nitro build, your server source maps will reference your original source files (#28521).
Note that one of the easiest ways of improving your build performance is to turn off source maps if you aren't using them, which you can do easily in your
nuxt.config
:🎁 New Features for Module Authors
In the run-up to Nuxt v4, we're working on adding some key functionality for module authors, including a new
isNuxtMajorVersion
utility where required (#27579) and better inferred typing for merged module options using the newdefineNuxtModule().with()
method (#27520).✨ Improved Dev Warnings
We no longer warn when using data fetching composables in middleware (#28604) and we warn when user components' names begin with Lazy (#27838).
🚨 Vue TypeScript Changes
For a while, in the Vue ecosystem, we've been augmenting
@vue/runtime-core
to add custom properties and more tovue
. However, this inadvertently breaks the types for projects that augmentvue
- which is now the officially recommended in the docs way to augment these interfaces (for example, ComponentCustomProperties, GlobalComponents and so on).This means all libraries must update their code (or it will break the types of libraries that augment
vue
instead).We've updated our types in Nuxt along these lines but you may experience issues with the latest
vue-router
when used with libraries which haven't yet done so.Please create an issue with a reproduction - I'll happily help create a PR to resolve in the upstream library in question. Or you may be able to work around the issue by creating a
declarations.d.ts
in the root of your project with the following code (credit):✅ 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
routes
function inrouter.options
(#27644)isNuxtMajorVersion
compatibility util (#27579).with
for better module options types (#27520)Lazy
(#27838)usePreviewMode
(#28371)prepend
option toaddRouteMiddleware
(#28496)__NUXT__
when using multi-app (#27263)🔥 Performance
decode
function only for named cookie (#28215)getCachedData
(#28472)🩹 Fixes
definePageMeta
in client-only pages (#28246)dist/runtime/
in tsconfig includes (#28237)assetsDir
(59f0099f4)serverDir
(#28249)vite-plugin-vue
(#28307)scroll-padding-top: auto
in scrollBehavior (#28320)runtimeConfig.public
is reactive on client (#28443)nuxt/scripts
(#28449)@vue/runtime-core
and@vue/runtime-dom
(#28446)baseURL
for public assets in dev (#28482)useFetch
(#28517)vue
, not sub-packages (#28542)route.meta
(#28441)validate
method (#28612)prefetchOn
prop (#28630)📖 Documentation
vue
lang to sample code (#28247)splitSetCookieString
fromcookie-es
(29f95ae0d)headers.getSetCookie
(45c6df9a4)bunx
->bun x
(#28277)@see
blocks (#28270)mountSuspended
(#28463)options
type in custom useFetch recipe (#28389)🏡 Chore
✅ Tests
pageTransition
in client-only page (#27839)SharedComponent
in server head (510f3e28f)🤖 CI
❤️ Contributors
v3.12.4
Compare Source
👉 Changelog
compare changes
🔥 Performance
resolveId
in layers (#27971)🩹 Fixes
noScripts
(#27972)/
as fallback if page can't be identified (e6109b226)html-validate
(#28024)unhead
key for ad-hoc module options (#28088)getNuxtVersion
returnsstring
(#28125)scroll-padding-top
in scrollBehavior (#28083)useAsyncData
returns undefined (#28154)getCachedData
null response (d10cea11b)app/
assrcDir
if it doesn't exist (#28176)serverDir
within layers using v4 compat (#28177)getCachedData
to return undefined (#28187)addEventListener
to register cookie store listener (#28193)set-cookie
headers (#28211)💅 Refactors
postcss
module loading (#27946)_registeredComponents
from ssrContext (#27819)errx
to handle dev log traces (#28027)📖 Documentation
nuxtApp.runWithContext
(#28000)pending
variable from data fetching docs (#28011)layers/
directory (#28128)✅ Tests
typeCheck
test in minimal build (#28166)🤖 CI
❤️ Contributors
v3.12.3
Compare Source
👉 Changelog
compare changes
🔥 Performance
fs-extra
(#27787)chokidar
when a customsrcDir
is provided (#27871)prefetchComponents
is treeshaken on server (#27905)🩹 Fixes
dir.app
(0c73cb734)navigateTo
called withopen
(#27742)refresh
type in server component refs (#27778)#vue-router
alias for backwards compat (#27896)nuxt
types (#27900)?raw
from head when in dev mode (#27940)💅 Refactors
performance.now
to measure time (d14f7ec46)📖 Documentation
refreshCookie
onuseCookie
doc page (#27744)main
branch (e7fbc9f81)useFetch
/AsyncData
in wrappers (#27785)vue-router
docs (#27895)compatibilityVersion
is available in the latest release (#27919)Nuxt 3
->Nuxt
orNuxt 3+
(3c16c890c)ref
s (#27933)🏡 Chore
4x
tag for v4 nightly releases (9d5dd5494)dev-bundler
(e3448fa0d)2.x
branch (8003cf72f)✅ Tests
🤖 CI
main
branch (7abd982f8)@vitejs/plugin-vue
again (56660cbdd)❤️ Contributors
v3.12.2
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 unjs ecosystem.
👉 Changelog
compare changes
🔥 Performance
🩹 Fixes
onNuxtReady
callback without arguments (#27428)app/
dir backwards compatibility (#27529)ssr: false
(#27542)runtimeConfig
key (9e56b60c6)#app/defaults
rather than augmenting (#27567)useRouteAnnouncer
(#27562)_installedModules
(e4bfea642)app.rootId
withapp.rootAttrs.id
(#27630)mergeProps
import in islands transform (#27622)vite.cacheDir
if defined (#27628)close
is called (#27637)/
even if pages module isn't enabled (dabcb5ecc)📖 Documentation
head
(#27575)clear()
function added in 3.11 (#27615)🏡 Chore
webpack-virtual-modules
(58dd7f3a6)✅ Tests
🤖 CI
❤️ Contributors
v3.12.1
Compare Source
👉 Changelog
compare changes
🩹 Fixes
@nuxt/scripts
(0252000d7)💅 Refactors
CompatibilityDateSpec
(#27521)📖 Documentation
🏡 Chore
nuxi
dependency (#27526)✅ Tests
❤️ Contributors
v3.12.0
Compare Source
👀 Highlights
We're on the road to the release of Nuxt 4, but we've not held back in Nuxt v3.12. A huge thank you to the 75+ Nuxt contributors and community members who have been part of this release. ❤️
🚀 Testing Nuxt 4 changes
Nuxt 4 is on the horizon, and it's now possible to test out the behaviour changes that will be coming in the next major release (#26925) by setting an option in your
nuxt.config
file:As we've been merging PRs for Nuxt 4, we've been enabling them behind this flag. As much as possible we're aiming for backwards compatibility - our test matrix is running the same fixtures in both v3 and v4 compatibility mode.
There is a lot to say here, with 10+ different PRs and behaviour changes documented and testable, but for full details, including migration steps, see the v4 upgrade documentation.
We'd be very grateful for early testing of what's coming in Nuxt 4! 🙏
📜 Nuxt Scripts a
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.