-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore(deps): update dependency nuxt to v3 #721
Conversation
|
Warning Rate limit exceeded@renovate[bot] has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 12 minutes and 46 seconds before requesting another review. How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
Not a bot task. See #337 |
Renovate Ignore NotificationBecause you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR. |
This PR contains the following updates:
2.18.1
->3.13.0
Release Notes
nuxt/nuxt (nuxt)
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 auto-install
We've been gradually working to release Nuxt Scripts. It's currently in public preview, but we're near a public release, so we've added some stubs for composables that (when used) will prompt installing the
@nuxt/scripts
module.👉 Watch out for the launch - and an article explaining more!
🌈 Layer auto-registration and bugfixes
Just like
~/modules
, any layers within your project in the~/layers
directory will now be automatically registered as layers in your project (#27221).We also now correctly load layer dependencies, which should resolve a range of issues with monorepos and git installations (#27338).
🌐 Built-in accessibility improvements
We now have a built-in
<NuxtRouteAnnouncer>
component and correspondinguseRouteAnnouncer
composable, which will be added by default to new Nuxt templates going forward.For full details, see the original PR (#25741) and documentation.
We're continuing to work on
nuxt/a11y
- expect to hear more on that in future!🔥 Performance improvements
We've landed some performance improvements as well, many of which are behind the
compatibilityVersion: 4
flag, such as a move away from deeply reactive asyncData payloads.Significant improvements include deduplicating modules (#27475) - which will apply mostly to layer users who specify modules in their layers. In one project, we saw 30s+ improvement in starting Nuxt.
We've also improved Vite dev server start up time by excluding common ESM dependencies from pre-bundling, and would suggest module authors consider doing the same (#27372).
We improved chunk determinism, so sequential builds should be less likely to have completely different chunk hashes (#27258).
And we tree shake more client-only composables from your server builds (#27044), and have reduced the size of server component payloads (#26863).
👨👩👧👦 Multi-app support
We've landed a couple of changes that take us toward a place of supporting multi-app natively in Nuxt, including a
multiApp
experimental flag (#27291) and the ability to have multiple Nuxt app instances running in parallel at runtime (#27068).While it's not yet ready, please do follow along on the tracker issue, and feel free to pitch in if this is interesting to you.
⛑️ DX wins
We now serialise more things in your dev server logs, including VNodes (#27309) and URLs. We also addressed a bug that could lead to a frozen dev server.
When accessing private runtime config in the browser, we now let you know with a more informative error message (#26441).
🪨 Stabilising features
We've removed some experimental options that have been stabilised and which we feel no longer need to be configurable:
experimental.treeshakeClientOnly
(enabled by default since v3.0.0)experimental.configSchema
(enabled by default since v3.3.0)experimental.polyfillVueUseHead
(disabled since v3.4.0) - implementable in user-land with pluginexperimental.respectNoSSRHeader
(disabled since v3.4.0) - implementable in user-land with server middlewareWe've also enabled
scanPageMeta
by default (#27134). This pulls out any page metadata in yourdefinePageMeta
macro, and makes it available to modules (like@nuxtjs/i18n
) so they can augment it.This unlocks much better module/typed routing integration, but has a potential performance cost - so please file an issue if you experience any problems.
💪 Type improvements
We now have support for typed
#fallback
slots in server components (#27097).We've also improved some defaults in your generated
tsconfig.json
, including settingmodule: 'preserve'
if you have a locally installed TypeScript v5.4 version (see docs) - see #26667, #27485.📦 Module author/power user improvements
We have shipped a range of type improvements for module authors, including:
installModule
(#26744)onPrehydrate
hook for hooking into the browser hydration cycle (#27037)useRuntimeConfig
andupdateRuntimeConfig
utils (#27117)🎨 Inlined UI templates
If you previously used
@nuxt/ui-templates
then it may be worth knowing that we have moved them from a separate repository into the nuxt/nuxt monorepo. (This is purely a refactor rather than a change, although you can expect some new designs for Nuxt v4.)✅ 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
useRequestURL
(#26687)imports.scan
option (#26576)<NuxtRouteAnnouncer>
anduseRouteAnnouncer
(#25741)resolvePath
andfindPath
(#26465)useLink
fromNuxtLink
(#26522)future.compatibilityVersion
(#26925)app.rootAttrs
andteleportAttrs
(#27014)cookieStore
by default (f597ca59a)onUpdated
andonUnmounted
on server (#27044)nuxt/scripts
on usage (#27010)<NuxtPage>
(#27050)renderSSRHeadOptions
config forunhead
(#26989)onPrehydrate
lifecycle hook (#27037)#fallback
slot to server components types (#27097)useRuntimeConfig
andupdateRuntimeConfig
utils (#27117)layers/
directory (#27221)appId
and improve chunk determinism (#27258)multiApp
flag (#27291)compatibilityVersion
(#27305)URL
serialiser for dev server logs (a549b46e9)this.$route
(#27313)installModule
(#26744).with
for better module options types (#26850)compatibilityDate
flag for future (#27512)🔥 Performance
asyncData
watch when unmounted (#26821)ssrContext.styles
reference (from unusedvue-style-loader
) (2d1ab61b2)shallowReactive
(#27214)🩹 Fixes
getCachedData
from shaping type ofuseAsyncData
(#25946)hasSuffix
(#26725)moduleDetection
to 'force' (#26667)nuxt._ignore
after all modules run (#26680)v-for
to slot in islands (#26880)_scope
is active before callingrun
function (#26756, #26904)enabled
isfalse
(#26906)lang="ts"
(#26912)updateAppConfig
(#26949)useState
inNuxtClientFallback
setup function (#26928).js
extension from template imports (0d4a622f3)runWithContext
(#26976)app.vue
exists inrootDir
(1af81ed0f)URL
constructor to resolve external protocols (5f0693a69)URL
for parsing URLs rather thanparseURL
([ea22d3f98](httpsConfiguration
📅 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.