-
-
Notifications
You must be signed in to change notification settings - Fork 19
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 nuxt core (minor) #176
Open
renovate
wants to merge
1
commit into
main
Choose a base branch
from
renovate/nuxt
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
2f2fe1c
to
db568ff
Compare
db568ff
to
9d6260f
Compare
5144be1
to
b616c9b
Compare
b616c9b
to
807d7f6
Compare
807d7f6
to
59f852b
Compare
59f852b
to
c2ab136
Compare
c2ab136
to
9850c7c
Compare
9850c7c
to
241cd80
Compare
241cd80
to
1844bc6
Compare
1844bc6
to
d851e46
Compare
d851e46
to
d7ccd9f
Compare
d7ccd9f
to
4479919
Compare
4479919
to
73b2b8f
Compare
fd71e30
to
683bfb8
Compare
683bfb8
to
19369a6
Compare
749744c
to
ee4d9c7
Compare
ee4d9c7
to
a32bc01
Compare
a32bc01
to
d6b0d31
Compare
d6b0d31
to
4f8e96e
Compare
e6d5e30
to
7e59671
Compare
7e59671
to
a5ec0d7
Compare
9d291c2
to
64d9336
Compare
64d9336
to
501f5da
Compare
501f5da
to
3f29811
Compare
3f29811
to
8e6555f
Compare
dce7685
to
f6cbedf
Compare
2a3f920
to
0e9e5bc
Compare
0e9e5bc
to
faea3aa
Compare
faea3aa
to
fabd355
Compare
91e0ff1
to
f331a4f
Compare
f331a4f
to
fbf2921
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.2.0
->^3.16.0
3.2.0
->3.17.2
Release Notes
nuxt/nuxt (@nuxt/kit)
v3.16.0
Compare Source
👀 Highlights
There's a lot in this one!
⚡️ A New New Nuxt
Say hello to
create-nuxt
, a new tool for starting Nuxt projects (big thanks to @devgar for donating the package name)!It's a streamlined version of
nuxi init
- just a sixth of the size and bundled as a single file with all dependencies inlined, to get you going as fast as possible.Starting a new project is as simple as:
Special thanks to @cmang for the beautiful ASCII-art. ❤️
Want to learn more about where we're headed with the Nuxt CLI? Check out our roadmap here, including our plans for an interactive modules selector.
🚀 Unhead v2
We've upgraded to
unhead
v2, the engine behind Nuxt's<head>
management. This major version removes deprecations and improves how context works:If you're using Unhead directly in your app, keep in mind:
#app/composables/head
instead of@unhead/vue
@unhead/vue
might lose async contextDon't worry though - we've maintained backward compatibility in Nuxt 3, so most users won't need to change anything!
If you've opted into
compatibilityVersion: 4
, check out our upgrade guide for additional changes.🔧 Devtools v2 Upgrade
Nuxt Devtools has leveled up to v2 (#30889)!
You'll love the new features like custom editor selection, Discovery.js for inspecting resolved configs (perfect for debugging), the return of the schema generator, and slimmer dependencies.
One of our favorite improvements is the ability to track how modules modify your Nuxt configuration - giving you X-ray vision into what's happening under the hood.
👉 Discover all the details in the Nuxt DevTools release notes.
⚡️ Performance Improvements
We're continuing to make Nuxt faster, and there are a number of improvements in v3.16:
exsolve
for module resolution (#31124) along with the rest of the unjs ecosystem (nitro, c12, pkg-types, and more) - which dramatically speeds up module resolutionloadNuxt
by skipping unnecessary resolution steps (#31176) - faster startupsoxc-parser
for parsing in Nuxt plugins (#30066)All these speed boosts happen automatically - no configuration needed!
Shout out to CodSpeed with Vitest benchmarking to measure these improvements in CI - it has been really helpful.
To add some anecdotal evidence, my personal site at roe.dev loads 32% faster with v3.16, and nuxt.com is 28% faster. I hope you see similar results! ⚡️
🕰️ Delayed Hydration Support
We're very pleased to bring you native delayed/lazy hydration support (#26468)! This lets you control exactly when components hydrate, which can improve initial load performance and time-to-interactive. We're leveraging Vue's built-in hydration strategies - check them out in the Vue docs.
You can also listen for when hydration happens with the
@hydrated
event:Learn more about lazy hydration in our components documentation.
🧩 Advanced Pages Configuration
You can now fine-tune which files Nuxt scans for pages (#31090), giving you more control over your project structure:
🔍 Enhanced Debugging
We've made debugging with the
debug
option more flexible! Now you can enable just the debug logs you need (#30578):Or keep it simple with
debug: true
to enable all these debugging features.🎨 Decorators Support
For the decorator fans out there (whoever you are!), we've added experimental support (#27672). As with all experimental features, feedback is much appreciated.
📛 Named Layer Aliases
It's been much requested, and it's here! Auto-scanned local layers (from your
~~/layers
directory) now automatically create aliases. You can access your~~/layers/test
layer via#layers/test
(#30948) - no configuration needed.If you want named aliases for other layers, you can add a name to your layer configuration:
This creates the alias
#layers/example-layer
pointing to your layer - making imports cleaner and more intuitive.🧪 Error Handling Improvements
We've greatly improved error messages and source tracking (#31144):
useAsyncData
calls with precise file location informationPlus, we're now using Nitro's beautiful error handling (powered by youch) to provide more helpful error messages in the terminal, complete with stacktrace support.
Nitro now also automatically applies source maps without requiring extra Node options, and we set appropriate security headers when rendering error pages.
📦 Module Development Improvements
For module authors, we've added the ability to augment Nitro types with
addTypeTemplate
(#31079):⚙️ Nitro v2.11 Upgrade
We've upgraded to Nitro v2.11. There are so many improvements - more than I can cover in these brief release notes.
👉 Check out all the details in the Nitro v2.11.0 release notes.
📦 New
unjs
Major VersionsThis release includes several major version upgrades from the unjs ecosystem, focused on performance and smaller bundle sizes through ESM-only distributions:
✅ Upgrading
As usual, our recommendation for upgrading is to run:
This refreshes your lockfile and pulls in all the latest dependencies that Nuxt relies on, especially from the unjs ecosystem.
👉 Changelog
compare changes
🚀 Enhancements
@nuxt/devtools
to v2 (#30889)NuxtPage
(#30704)directoryToURL
to normalise paths (#30986)start
/set
in loading indicator (#30989)pages/
(#31090)NuxtLink
slot (#31104)addTypeTemplate
(#31079)oxc-parser
instead of esbuild + acorn (#30066)🔥 Performance
exsolve
for module resolution (#31124)loadNuxt
(#31176)🩹 Fixes
<NuxtLayout>
fallback
prop is typed (#30832)keepalive
cache reset (#30807)div
wrapper in client-only pages (#30425)nitropack
(aba75bd5a)null
from resolve functions (d68e8ce57)app.head.meta
values are undefined (#30959)shared/
directories available within layers (#30843)<pre>
when rendering dev errors (9aab69ec4)page:transition:start
type (#31040)provide
/inject
work insetup
ofdefineNuxtComponent
(#30982)_
for NuxtIsland name on server pages (#31072)ohash
to calculate legacy async data key without hash (#31087)shared
dir from config (#31091)nuxt.options.pages
to detected configuration (#31101)definePageMeta
does not receive an object (#31156)no-ssr
middleware handler (a99c59fbd)navigate
withvue-router
(7a1934509)nuxt.options.pages
(fa480e0a0)resolveModule
(6fb5c9c15)resolveTypePath
(a0f9ddfe2)compilerOptions.paths
(835e89404)RawVueCompilerOptions
for unresolvedtsconfig
(#31202)navigateTo
with replace (#31244)devStorage
(#31233)useFetch
function name on server for warning (#31213)x-nitro-prerender
header (2476cab9a)💅 Refactors
isEqual
fromohash/utils
(2e27cd30c)noScripts
route rule (#31083)runtime/nitro
files (#31131)📖 Documentation
spaLoadingTemplate
example (#30830)NuxtPage
(#30781)navigateTo
docs with clearer structure and examples (#30876)rootDir
(27e356fe6)vue:setup
andapp:data:refresh
hooks (#31001)defineNuxtRouteMiddleware
(#31005)port
option to preview command (#30999).nuxtrc
documentation (#31093)$fetch
on the server (#31114)create nuxt
command (fe82af4c9)3x
(a243f8fcf)<NuxtPage>
during page changes (#31116)typedPages
in unhoisted pnpm setups (#31262)📦 Build
🏡 Chore
errx
dependency (566418177)@nuxtjs/mdc
typechecking dep (f23683b26)nitro/renderer
templates (b29c0e86b)✅ Tests
#internal/nitro/app
(a1b855cc5)❤️ Contributors
v3.15.4
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
🩹 Fixes
acorn
(#30754)@nuxt/schema
fromnuxt
package dir (#30774)srcDir
(#30771)useRoute
in SFC setup (#30788)externality
for dev server externals (#30802)💅 Refactors
chunk.names
for asset names (#30780)❤️ Contributors
v3.15.3
Compare Source
👀 Highlights
CORS configuration for dev server
Alongside a range of improvements, we've also shipped a significant fix to impose CORS origin restrictions on the dev server. This applies to your Vite or Webpack/Rspack dev middleware only.
This is a significant/breaking change we would not normally ship in a patch but it is a security fix (see GHSA-4gf7-ff8x-hq99 and GHSA-2452-6xj8-jh47) and we urge you to update ASAP.
You can configure the allowed origins and other CORS options via the
devServer.cors
options in yournuxt.config
, which may be relevant if you are developing with a custom hostname:✅ 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
mkdirSync
calls (#30651)findPath
andresolvePath
(#30682)Transition
component only on client side (#30720)🩹 Fixes
#app-manifest
alias (#30618)plugin.src
for variable name generation (#30649)dev
/test
environment value (#30667)invalidateModule
call (9bd71e498)[[
optional dynamic params (#30619)devServer.cors
(406db5b4d)💅 Refactors
externality
and use vite internal config (#30634)📖 Documentation
useFetch
example (#30629)nuxi
source code (4fabe0025)NuxtLink
(#30614)addRouteMiddleware
(#30656)ClientOnly
withonMounted
hook (#30670)navigation
mode incallOnce
composable (#30612)📦 Build
inlineDependencies
option (01adefcec)🏡 Chore
lodash-es
(0c01273f5)🤖 CI
❤️ Contributors
v3.15.2
Compare Source
👀 Highlights
🔥 Startup performance improvements
It is worth noting that this release includes some pretty significant performance improvements which you should notice particularly in the startup time. In my tests in the nuxt monorepo,
There's more improvement to do here but hopefully these are good numbers!
📦 CLI refactor
To improve performance within Nuxt projects, we've published a new
@nuxt/cli
distribution ofnuxi
, which is used under-the-hood innuxt
(see issue). This should behave exactly the same and nothing needs to be updated in your projects (for example, you will continue to use thenuxi
ornuxt
commands). The only significant change is that it no longer inlines dependencies. Feedback is welcome 🙏✅ 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
@nuxt/cli
dependency (#30526)🩹 Fixes
definePageMeta
when extracting page metadata (#30490)#build
to the end oftsConfig
paths (#30520)fullPath
instead of empty string in router hmr (#30500)@nuxt/cli
(618bbc6da)page:loading:end
only once with nested pages (#29009)#app-manifest
(#30587)shouldPrefetch
on the server side (#30591)💅 Refactors
📖 Documentation
--dev
option for the module command (#30477)url
inuseFetch
(#30531)@nuxt/module-builder
source (509cf4a5c)status
detail and enhancegetCachedData
readability (#30536)useNuxtData
(#30570)useAsyncData
side effects (#30479)🏡 Chore
nuxt/app
(1adf3e31f)🤖 CI
❤️ Contributors
v3.15.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 unjs ecosystem.
👉 Changelog
compare changes
🔥 Performance
lodash-es
dependency (#30409)pathe
browser dep for deep server components (#30456)🩹 Fixes
nuxt
instance toresolvePagesRoutes
(e4a372e12)location
instead ofrange
for route meta property extraction (#30447)vueCompilerOptions.plugins
type (#30454)baseURL
when ignoring prerendered manifest (#30446)router.options
when hmring routes (#30455)💅 Refactors
consola
withnuxt
tag instead of console (#30408)📖 Documentation
lodash
and recommendes-toolkit
(8e2ca5bdc)🏡 Chore
❤️ Contributors
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 newmode: '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
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)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.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.