chore(deps): update nuxt framework to ^3.15.0 #415
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:
^3.14.1592
->^3.15.0
^3.14.1592
->^3.15.0
^3.14.1592
->^3.15.0
^3.13.1
->^3.15.0
Release Notes
nuxt/nuxt (@nuxt/kit)
v3.15.0
Compare Source
👀 Highlights
❄️ Snowfall!
Happy holidays! You'll notice when you start Nuxt that (if you're in the Northern Hemisphere) there's some snow on the loading screen (#29871).
⚡️ Vite 6 included
Nuxt v3.15 includes Vite 6 for the first time. Although this is a major version, we expect that this won't be a breaking change for Nuxt users (see full migration guide). However, please take care if you have dependencies that rely on a particular Vite version.
One of the most significant changes with Vite 6 is the new Environment API, which we hope to use in conjunction with Nitro to improve the server dev environment. Watch this space!
You can read the full list of changes in the Vite 6 changelog.
🪵 Chromium devtools improvements
We talk a lot about the Nuxt DevTools, but v3.15 ships with better integration in dev mode for Chromium-based browser devtools.
We now use the Chrome DevTools extensibility API to add support for printing nuxt hook timings in the browser devtools performance panel.
🗺️ Navigation mode for
callOnce
callOnce` is a built-in Nuxt composable for running code only once. For example, if the code runs on the server it won't run again on the client. But sometimes you do want code to run on _every navigation_ - just avoid the initial server/client double load. For this, there's a new
mode: 'navigation'` option that will run the code only once _per navigation_. (See #30260 for more info.)🥵 HMR for templates, pages + page metadata
We now implement hot module reloading for Nuxt's virtual files (like routes, plugins, generated files) as well as for the content of page metadata (within a
definePageMeta
macro) (#30113).This should mean you have a faster experience in development, as well as not needing to reload the page when making changes to your routes.
📋 Page meta enhancements
We now support extracting extra page meta keys (likely used by module authors) via
experimental.extraPageMetaExtractionKeys
(#30015). This enables module authors to use this information at build time, in thepages:resolved
hook.We also now support local functions in
definePageMeta
(#30241). This means you can do something like this:🔥 Performance improvements
We now preload the app manifest in the browser if it will be used when hydrating the app (#30017).
We'll also tree shake vue-router's hash mode history out of your bundle if we can - specifically, if you haven't customised your
app/router.options.ts
(#30297).🐣 v4 updates
If A few more changes shipped for the new defaults for v4, including only inlining styles by default for Vue components (#30305).
✅ 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
extraPageMetaExtractionKeys
(#30015)definePageMeta
(#30241)mode: 'navigation'
tocallOnce
(#30260)🔥 Performance
hashMode
option (#30297)🩹 Fixes
addServerTemplate
(a02af2348)extraExtractionKeys
on runtimeroute.meta
(ae9f42f4a)style
value for head components (#29999)useId
implementation (40f437d25)buildDir
tonormalizeTemplate
(#30115)useRequestFetch
(#30117)nitropack
rather thannitro
import (2d5b53b23)engines.node
to match dependencies (#30139)routerOptions.history
to return null (#30192)useId
for island client component teleport id (#30151)nuxt
andnuxt/app
(#30148)getRouteRules
works with nitro signature (#30277)replace
in middleware withnavigateTo
(#30283)nitropack
(f220314a5)<RouterLink>
for links starting with#
(#30190)#app-manifest
(ec613e533)useId
forclient-fallback
component uid (#30314)@vitest/
(4171a1076)addTemplate
if undefined (#30348)import.meta.hot.data
(b1cf5781d)💅 Refactors
composable-keys
plugin into nuxt core (#30029)nuxt:
(#30028)📖 Documentation
event.waitUntil
(#29583)vite.dev
(#30111)nuxi upgrade
channel flag (#30184)useLazyFetch
(#30171)vite.css.preprocessorMaxWorkers
(eb1ba017c)compatibilityVersion
feature flag (#30274)nuxi
command pages (#30199)inlineStyles
(2660bffbc)🏡 Chore
unimport
(7ee455969)installed-check
dependency (0e84cb9a4)engines.node
to reflect only deps (d3d276919)rimraf
(cf9d82c5a)div
wrapper in client-only page (#30359)✅ Tests
🤖 CI
❤️ Contributors
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 becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
This PR was generated by Mend Renovate. View the repository job log.