-
-
Notifications
You must be signed in to change notification settings - Fork 10
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 all non-major dependencies #511
Merged
Merged
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
Thank you for following the naming conventions! 🙏 |
commit: |
✅ Deployed shelve-vault
|
Edited/Blocked NotificationRenovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR. You can manually request rebase by checking the rebase/retry box above. |
✅ Deployed shelve-lp
|
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:
1.2.27
->1.2.28
1.2.26
->1.2.27
^0.4.3
->^0.4.5
2.1.1
->2.2.1
0.10.5
->0.11.0
0.8.17
->0.8.18
12.7.0
->12.8.2
12.7.0
->12.8.2
9.21.0
->9.22.0
^0.11.0-beta.4
->^0.11.2
^3.15.4
->^3.16.0
3.15.4
->3.16.0
10.5.2
->10.6.1
5.7.3
->5.8.2
3.0.7
->3.0.8
^3.111.0
->^3.114.0
Release Notes
nuxt/devtools (@nuxt/devtools)
v2.2.1
Compare Source
Bug Fixes
v2.2.0
Compare Source
Features
vite-plugin-vue-tracer
(#803) (faa08d3)2.1.3 (2025-03-03)
2.1.2 (2025-03-03)
2.1.1 (2025-02-28)
Bug Fixes
Features
v2.1.3
Compare Source
nuxt/scripts (@nuxt/scripts)
v0.11.0
Compare Source
Breaking Changes
New Nuxt Version Requirement
The latest Nuxt Scripts now requires Nuxt v3.16. Please upgrade using
nuxi upgrade --force
.Updated
useScript()
🚦 Impact Level: High
script.proxy
is rewritten for simpler, more stable behaviorstub()
and runtime hookscript:instance-fn
are removedReplacing promise usage
If you're using the script as a promise you should instead opt to use the
onLoaded()
functions.Replacing proxy usage
If you're accessing the underlying API directly from the script instance, you will now need to only access it from the
.proxy
.Replacing
stub()
If you were using stub for anything you should replace this with either custom
use()
behavior.What's Changed
Full Changelog: nuxt/scripts@v0.10.5...v0.11.0
nuxt-hub/core (@nuxthub/core)
v0.8.18
Compare Source
compare changes
📖 Documentation
🏡 Chore
nodeCompat
(0c9eb8b)❤️ Contributors
vueuse/vueuse (@vueuse/core)
v12.8.2
Compare Source
🐞 Bug Fixes
View changes on GitHub
v12.8.1
Compare Source
🐞 Bug Fixes
View changes on GitHub
v12.8.0
Compare Source
🚀 Features
MaybeRef
andMaybeRefOrGetter
in favor of Vue's native - by @ilyaliao and @antfu in https://github.com/vueuse/vueuse/issues/4636 (7432f)options.deepRefs
- by @OrbisK and @antfu in https://github.com/vueuse/vueuse/issues/4591 (9afee)retried
to theautoReconnect.retries
- by @9romise and @OrbisK in https://github.com/vueuse/vueuse/issues/4604 (73e6d)🐞 Bug Fixes
variable
when initial - by @ilyaliao in https://github.com/vueuse/vueuse/issues/4641 (d680f)granted
- by @Nikitatopodin and Никита Быковский in https://github.com/vueuse/vueuse/issues/4559 (f9685)View changes on GitHub
eslint/eslint (eslint)
v9.22.0
Compare Source
nuxt/nuxt (nuxt)
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
pnpm/pnpm (pnpm)
v10.6.1
Compare Source
Patch Changes
--silent
reporting is used.--loglevel
is set toerror
, don't show installation summary, execution time, and big tarball download progress.package.json
#9226.approve-builds
command, if package.json containsonlyBuiltDependencies
orignoredBuiltDependencies
, the selected dependency package will continue to be written intopackage.json
.v10.6.0
Compare Source
Minor Changes
pnpm-workspace.yaml
can now hold all the settings that.npmrc
accepts. The settings should use camelCase #9211.pnpm-workspace.yaml
example:Projects using a
file:
dependency on a local tarball file (i.e..tgz
,.tar.gz
,.tar
) will see a performance improvement during installation. Previously, using afile:
dependency on a tarball caused the lockfile resolution step to always run. The lockfile will now be considered up-to-date if the tarball is unchanged.Patch Changes
pnpm self-update
should not leave a directory with a broken pnpm installation if the installation fails.fast-glob
replace withtinyglobby
to reduce the size of the pnpm CLI dependencies #9169.pnpm deploy
should not remove fields from the deployed package'spackage.json
file #9215.pnpm self-update
should not read the pnpm settings from thepackage.json
file in the current working directory.pnpm deploy
creating apackage.json
without theimports
andlicense
field #9193.pnpm update -i
should list only packages that have newer versions #9206.catalogs
section of thepnpm-lock.yaml
file to be removed whendedupe-peer-dependents=false
on a filtered install. #9112microsoft/TypeScript (typescript)
v5.8.2
Compare Source
vitest-dev/vitest (vitest)
v3.0.8
[Compar
Configuration
📅 Schedule: Branch creation - "after 2am and before 3am" (UTC), Automerge - "after 1am and before 2am" (UTC).
🚦 Automerge: Enabled.
♻ 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.