-
-
Notifications
You must be signed in to change notification settings - Fork 2
chore(deps): update all non-major dependencies #90
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
Conversation
❌ Deploy Preview for ts-maps failed. Why did it fail? →
|
|
🤖 Auto-closing obsolete PR This PR was automatically closed because the dependency files it references are no longer present in the project. Removed files:
If this was closed in error, please reopen the PR and update the dependency files accordingly. |
1 similar comment
|
🤖 Auto-closing obsolete PR This PR was automatically closed because the dependency files it references are no longer present in the project. Removed files:
If this was closed in error, please reopen the PR and update the dependency files accordingly. |
This PR contains the following updates:
^2.6.2->^2.6.3^4.0.3->^4.1.1^4.0.3->^4.1.1^0.1.17->^0.1.78^0.1.8->^0.1.18^6.7.0->^6.8.0^1.2.20->^1.2.21^19.1.10->^19.1.12^19.1.7->^19.1.9^5.0.1->^5.0.2^0.9.4->^0.9.5^1.2.20->^1.2.21^16.1.5->^16.1.620.19.4->20.19.5^4.0.3->^4.1.1^4.0.3->^4.1.12.35.3->2.35.4^6.3.5->^6.3.6^3.5.18->^3.5.21^3.5.18->^3.5.214->4.5.1Release Notes
nuxt/devtools (@nuxt/devtools)
v2.6.3Compare Source
nuxt/nuxt (@nuxt/kit)
v4.1.1Compare Source
✅ Upgrading
Our recommendation for upgrading is to run:
This will deduplicate your lockfile as well, and help ensure that you pull in updates from other dependencies that Nuxt relies on, particularly in the unjs ecosystem.
👉 Changelog
compare changes
🩹 Fixes
globalThisoverwindow(#33125)deps.inline(#33133)useRouteusage warning (#33039)imports:sourcesin override warning (#33050)📖 Documentation
--to bun create command (5e661f0ca)app/prefix in lots of cases (#33117)navigateTo(#21442)🏡 Chore
rou3github url (#33130).tsextension (db9d840e1)🤖 CI
4xtags from releases (1cd8a6857)❤️ Contributors
v4.1.0Compare Source
👀 Highlights
🔥 Build and Performance Improvements
🍫 Enhanced Chunk Stability
Build stability has been significantly improved with import maps (#33075). This prevents cascading hash changes that could invalidate large portions of your build when small changes are made:
By default, JS chunks emitted in a Vite build are hashed, which means they can be cached immutably. However, this can cause a significant issue: a change to a single component can cause every hash to be invalidated, massively increasing the chance of 404s.
In short:
Obviously this wasn't optimal. With this new feature, the hash of (otherwise) unchanged files which import the entry won't be affected.
This feature is automatically enabled and helps maintain better cache efficiency in production. It does require native import map support, but Nuxt will automatically disable it if you have configured
vite.build.targetto include a browser that doesn't support import maps.And of course you can disable it if needed:
🦀 Experimental Rolldown Support
Nuxt now includes experimental support for
rolldown-vite(#31812), bringing Rust-powered bundling for potentially faster builds.To try Rolldown in your Nuxt project, you need to override Vite with the rolldown-powered version since Vite is a dependency of Nuxt. Add the following to your
package.json:npm:
{ "overrides": { "vite": "npm:rolldown-vite@latest" } }pnpm:
{ "pnpm": { "overrides": { "vite": "npm:rolldown-vite@latest" } } }yarn:
{ "resolutions": { "vite": "npm:rolldown-vite@latest" } }bun:
{ "overrides": { "vite": "npm:rolldown-vite@latest" } }After adding the override, reinstall your dependencies. Nuxt will automatically detect when Rolldown is available and adjust its build configuration accordingly.
For more details on Rolldown integration, see the Vite Rolldown guide.
🧪 Improved Lazy Hydration
Lazy hydration macros now work without auto-imports (#33037), making them more reliable when component auto-discovery is disabled:
This ensures that components that are not "discovered" through Nuxt (e.g., because
componentsis set tofalsein the config) can still be used in lazy hydration macros.📄 Enhanced Page Rules
If you have enabled experimental extraction of route rules, these are now exposed on a dedicated
rulesproperty onNuxtPageobjects (#32897), making them more accessible to modules and improving the overall architecture:The
defineRouteRulesfunction continues to work exactly as before, but now provides better integration possibilities for modules.🚀 Module Development Enhancements
Module Dependencies and Integration
Modules can now specify dependencies and modify options for other modules (#33063). This enables better module integration and ensures proper setup order:
This replaces the deprecated
installModulefunction and provides a more robust way to handle module dependencies with version constraints and configuration merging.🪝 Module Lifecycle Hooks
Module authors now have access to two new lifecycle hooks:
onInstallandonUpgrade(#32397). These hooks allow modules to perform additional setup steps when first installed or when upgraded to a new version:The hooks are only triggered when both
nameandversionare provided in the module metadata. Nuxt uses the.nuxtrcfile internally to track module versions and trigger the appropriate hooks. (If you haven't come across it before, the.nuxtrcfile should be committed to version control.)🙈 Enhanced File Resolution
The new
ignoreoption forresolveFiles(#32858) allows module authors to exclude specific files based on glob patterns:📂 Layer Directories Utility
A new
getLayerDirectoriesutility (#33098) provides a clean interface for accessing layer directories without directly accessing private APIs:✨ Developer Experience Improvements
🎱 Simplified Kit Utilities
Several kit utilities have been improved for better developer experience:
addServerImportsnow supports single imports (#32289):🔥 Performance Optimizations
This release includes several internal performance optimizations:
🐛 Notable Fixes
useFetchhook typing (#32891)<NuxtTime>(#32893)✅ Upgrading
As usual, our recommendation for upgrading is to run:
This will refresh your lockfile and pull in all the latest dependencies that Nuxt relies on, especially from the unjs ecosystem.
👉 Changelog
compare changes
🚀 Enhancements
ignoreoption toresolveFiles(#32858)onInstallandonUpgrademodule hooks (#32397)rolldown-vite(#31812)defineRouteRulesto pagerulesproperty (#32897)getLayerDirectoriesutil and refactor to use it (#33098)🔥 Performance
🩹 Fixes
satisfiesin page augmentation (#32902)useFetchhooks (#32891)resolvePathand normalize file extensions (#32857)requestTimeout+ allow configuration (#32874)node_modules/if no customsrcDir(#32987)routeobject (#32899)defineNuxtModule().with()(#33081)nuxtApp._runningTransitionon resolve (#33025)💅 Refactors
async/awaitinafterEach(#32999)📖 Documentation
setupTimeoutand addteardownTimeout(#32868)webRootto use new app directory (df7177bff)app/directory in layer guide (eee55ea41)--nightlycommand (#32907)features.inlineStylesdefault value (6ff3fbebb)useRouteand accessing route in middleware (#33004)🏡 Chore
type: 'module'in playground (#33099)✅ Tests
import.meta.dev(#33023)findWorkspaceDirrather than relative paths to repo root (a6dec5bd9)expect.poll(53fb61d5d)expect.pollinstead ofexpectWithPolling(357492ca7)vi.waitUntilinstead of custom retry logic (611e66a47)🤖 CI
❤️ Contributors
stacksjs/bumpx (@stacksjs/bumpx)
v0.1.78Compare Source
No significant changes
View changes on GitHub
v0.1.77Compare Source
No significant changes
View changes on GitHub
v0.1.76Compare Source
No significant changes
View changes on GitHub
v0.1.75Compare Source
No significant changes
View changes on GitHub
v0.1.74Compare Source
No significant changes
View changes on GitHub
v0.1.71Compare Source
No significant changes
View changes on GitHub
v0.1.70Compare Source
No significant changes
View changes on GitHub
v0.1.69Compare Source
No significant changes
View changes on GitHub
v0.1.68Compare Source
🚀 Features
🐞 Bug Fixes
View changes on GitHub
v0.1.65Compare Source
No significant changes
View changes on GitHub
v0.1.61Compare Source
No significant changes
View changes on GitHub
v0.1.60Compare Source
No significant changes
View changes on GitHub
v0.1.59Compare Source
No significant changes
View changes on GitHub
v0.1.58Compare Source
No significant changes
View changes on GitHub
v0.1.57Compare Source
No significant changes
View changes on GitHub
v0.1.56Compare Source
No significant changes
View changes on GitHub
v0.1.55Compare Source
No significant changes
View changes on GitHub
v0.1.54Compare Source
No significant changes
View changes on GitHub
v0.1.53Compare Source
No significant changes
View changes on GitHub
v0.1.52Compare Source
No significant changes
View changes on GitHub
v0.1.46Compare Source
No significant changes
View changes on GitHub
v0.1.45Compare Source
No significant changes
View changes on GitHub
v0.1.38Compare Source
No significant changes
View changes on GitHub
v0.1.37Compare Source
No significant changes
View changes on GitHub
v0.1.36Compare Source
No significant changes
View changes on GitHub
v0.1.35Compare Source
No significant changes
View changes on GitHub
v0.1.34Compare Source
🐞 Bug Fixes
View changes on GitHub
v0.1.33Compare Source
No significant changes
View changes on GitHub
v0.1.32Compare Source
No significant changes
View changes on GitHub
v0.1.30Compare Source
No significant changes
View changes on GitHub
v0.1.29Compare Source
No significant changes
View changes on GitHub
v0.1.28Compare Source
No significant changes
View changes on GitHub
v0.1.27Compare Source
No significant changes
View changes on GitHub
v0.1.26Compare Source
No significant changes
View changes on GitHub
v0.1.25Compare Source
No significant changes
View changes on GitHub
v0.1.24Compare Source
No significant changes
View changes on GitHub
v0.1.23Compare Source
No significant changes
View changes on GitHub
v0.1.22Compare Source
No significant changes
View changes on GitHub
v0.1.21Compare Source
No significant changes
View changes on GitHub
v0.1.20Compare Source
No significant changes
View changes on GitHub
v0.1.19Compare Source
No significant changes
View changes on GitHub
v0.1.18Compare Source
No significant changes
View changes on GitHub
stacksjs/logsmith (@stacksjs/logsmith)
v0.1.18Compare Source
No significant changes
View changes on GitHub
v0.1.15Compare Source
No significant changes
View changes on GitHub
v0.1.14Compare Source
No significant changes
View changes on GitHub
v0.1.11Compare Source
No significant changes
View changes on GitHub
[
v0.1.10](https:/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.
👻 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.