chore(deps): update all non-major dependencies #635
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:
19.6.0
->19.8.0
19.6.0
->19.8.0
0.7.1
->0.7.6
3.14.1592
->3.16.0
22.9.1
->22.13.10
19.6.0
->19.8.0
9.15.0
->9.22.0
5.2.1
->5.2.3
15.2.10
->15.4.3
3.14.1592
->3.16.0
1.49.0
->1.51.0
1.7.0
->1.8.0
10.1.1
->10.1.5
3.3.3
->3.5.3
16.10.0
->16.15.0
1.5.0
->1.6.3
2.1.5
->2.1.9
1.6.9
->1.7.6
Release Notes
conventional-changelog/commitlint (@commitlint/cli)
v19.8.0
Compare Source
Performance Improvements
node:
prefix to bypass require.cache call for builtins (#4302) (0cd8f41)19.7.1 (2025-02-02)
Note: Version bump only for package @commitlint/cli
19.6.1 (2024-12-15)
Note: Version bump only for package @commitlint/cli
v19.7.1
Compare Source
Note: Version bump only for package @commitlint/cli
v19.6.1
Compare Source
Note: Version bump only for package @commitlint/cli
conventional-changelog/commitlint (@commitlint/config-conventional)
v19.8.0
Compare Source
Performance Improvements
node:
prefix to bypass require.cache call for builtins (#4302) (0cd8f41)19.7.1 (2025-02-02)
Note: Version bump only for package @commitlint/config-conventional
v19.7.1
Compare Source
Note: Version bump only for package @commitlint/config-conventional
nuxt/eslint (@nuxt/eslint)
v0.7.6
Compare Source
🚀 Features
View changes on GitHub
v0.7.5
Compare Source
No significant changes
View changes on GitHub
v0.7.4
Compare Source
🚀 Features
View changes on GitHub
v0.7.3
Compare Source
🐞 Bug Fixes
vue/singleline-html-element-content-newline
- by @DamianGlowala in https://github.com/nuxt/eslint/issues/526 (281d0)View changes on GitHub
v0.7.2
Compare Source
🚀 Features
View changes on GitHub
nuxt/nuxt (@nuxt/webpack-builder)
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)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.