Update all non-major dependencies #123
Open
+734
−492
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:
^0.18.0
->^0.19.1
^3.15.4
->^3.17.1
^3.15.4
->^3.17.1
22.13.5
->22.15.3
5.2.1
->5.2.3
^3.0.6
->^3.1.2
v4.2.0
->v4.4.0
15.4.3
->15.5.1
10.4.1
->10.10.0
8.3.6
->8.4.0
5.7.3
->5.8.3
6.1.1
->6.3.4
3.0.6
->3.1.2
5.98.0
->5.99.7
Release Notes
projectfluent/fluent.js (@fluent/bundle)
v0.19.1
: 2025-04-02Compare Source
@fluent/bundle 0.19.1
v0.19.0
: 2025-03-25Compare Source
@fluent/bundle 0.19.0
nuxt/nuxt (@nuxt/kit)
v3.17.1
Compare 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
execute
when non-immediate fetch key changes (#31941)escapeHTML
from vue (8e4b8d62f)@vue/shared
dependency (7d445c963)📦 Build
🏡 Chore
✅ Tests
❤️ Contributors
v3.17.0
Compare Source
👀 Highlights
This release brings a major reworking of the async data layer, a new built-in component, better warnings, and performance improvements!
📊 Data Fetching Improvements
A major reorganization of Nuxt's data fetching layer brings significant improvements to
useAsyncData
anduseFetch
.Although we have aimed to maintain backward compatibility and put breaking changes behind the
experimental.granularCachedData
flag (disabled by default), we recommend testing your application thoroughly after upgrading. You can also disableexperimental.purgeCachedData
to revert to the previous behavior if you are relying on cached data being available indefinitely after components usinguseAsyncData
are unmounted.👉 Read the the original PR for full details (#31373), but here are a few highlights.
Consistent Data Across Components
All calls to
useAsyncData
oruseFetch
with the same key now share the underlying refs, ensuring consistency across your application:This solves various issues where components could have inconsistent data states.
Reactive Keys
You can now use computed refs, plain refs, or getter functions as keys:
Optimized Data Refetching
Multiple components watching the same data source will now trigger only a single data fetch when dependencies change:
🎭 Built-In Nuxt Components
<NuxtTime>
- A new component for safe time displayWe've added a new
<NuxtTime>
component for SSR-safe time display, which resolves hydration mismatches when working with dates (#31876):The component accepts multiple time formats and gracefully handles both client and server rendering.
Enhanced
<NuxtErrorBoundary>
The
<NuxtErrorBoundary>
component has been converted to a Single File Component and now exposeserror
andclearError
from the component - as well as in the error slot types, giving you greater ability to handle errors in your templates and viauseTemplateRef
(#31847):🔗 Router Improvements
<NuxtLink>
now accepts atrailingSlash
prop, giving you more control over URL formatting (#31820):🔄 Loading Indicator Customization
You can now customize the loading indicator with new props directly on the component (#31532):
hideDelay
: Controls how long to wait before hiding the loading barresetDelay
: Controls how long to wait before resetting loading indicator state📚 Documentation as a Package
The Nuxt documentation is now available as an npm package! You can install
@nuxt/docs
to access the raw markdown and YAML content used to build the documentation website (#31353).💻 Developer Experience Improvements
We've added several warnings to help catch common mistakes:
runtimeConfig.app
namespace #31774definePageMeta
is used more than once in a file #31634🔌 Enhanced Module Development
Module authors will be happy to know:
experimental.enforceModuleCompatibility
allows Nuxt to throw an error when a module is loaded that isn't compatible with it (#31657). It will be enabled by default in Nuxt v4.addComponentExports
#27155🔥 Performance Improvements
Several performance improvements have been made:
tinyglobby
for faster file globbing #31668.data
directory from type-checking for faster builds #31738purgeCachedData
check #31785✅ Upgrading
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
hideDelay
andresetDelay
props for loading indicator (#31532)@nuxt/docs
(#31353)loadNuxtConfig
to nitro (#31680)runtimeConfig.app
namespace (#31774)middleware
when scanning page metadata (#30708)addComponentExports
(#27155)<NuxtErrorBoundary>
to SFC + exposeerror
/clearError
(#31847)<NuxtTime>
component for ssr-safe time display (#31876)trailingSlash
prop to<NuxtLink>
(#31820)🔥 Performance
tinyglobby
(#31668).data
directory from type-checking (#31738)purgeCachedData
check to improve tree-shaking (#31785)oxc-parser
manual wasm fallback logic (#31484)🩹 Fixes
modulesDir
paths are added tofs.allow
(#31540)/_nuxt/
(#31646)useLazyAsyncData
(#31676)error.url
(#31679)app:rendered
is called (#31686)fallback
attribute when stripping<DevOnly>
(c1d735c27)noScripts
(c9572e953)compatibilityDate
(#31725)statusMessage
when rendering html error (#31761)definePageMeta
is used more than once (#31634)error.data
before renderingerror.vue
(#31571)useAsyncData
in console log (#31801)NuxtErrorBoundary
error (#31791)preserveModules
(#31839)pending
withstatus
value for v4 (#25864)nuxt/app
in generated middleware and layouts declarations (#31808)withoutBase
(f956407bb)vue
in vite-node dev server (f3882e004)tsconfig.json
(#31882)useNuxtData
(#31893)useFetch
watch sources (#31903)modulesDir
to store build cache files (#31907)💅 Refactors
shallowRef
for primitives as well (#31662)_replaceAppConfig
when applying hmr (#31786)ConfigSchema
(#31894)📖 Documentation
app.vue
(#31645)templateParams
to seo docs (#31583)useHydration
(#31712)callOnce
returning value (#31747)vs.
consistently (#31760)addServerHandler
example (#31769)📦 Build
vue-sfc-transformer
to process sfcs (#31691)🏡 Chore
✅ Tests
<NuxtErrorBoundary>
(4df92c45f)pendingWhenIdle
(08f2224c8)🤖 CI
❤️ Contributors
v3.16.2
Compare 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
🔥 Performance
useRequestEvent
on client (#31586)🩹 Fixes
<Body>
and<Html>
(#31513)/index
is the last segment (#31528)page:loading:end
hook before navigation (#31504)document.cookie
(#31517)resolveComponent
(#31526)_nuxt/
paths in development (#31543)error.vue
(#31573)unhead
v2 api in default welcome + error pages (#31584)scanPageMeta
is disabled (0ba454b21)💅 Refactors
<NuxtPage>
(#31561)useServerHead
inonPrehydrate
withuseHead
(#31585)📖 Documentation
useTemplateRef
(#31458)$fetch
(#31459)dedupe
flag (#31467)refreshNuxtData
docs (#31448)--
before--template
(#31469)resolveComponent
only auto-imports components with literal strings (#31511)tsconfig.json
(#31473)page:start
andpage:finish
hooks (#31570)🏡 Chore
✅ Tests
❤️ Contributors
v3.16.1
Compare Source
compare changes
🔥 Performance
🩹 Fixes
mocked-exports
(#31295)typedPages
implementation (#31331)📖 Documentation
app.head
example (#31350)addServerTemplate
to modules guide (#31369)rspack
and removetest-utils
for monorepo guide (#31371)ini
syntax block highlighting for.env
files (f79fabe46)useHydration
docs (#31427)🏡 Chore
✅ Tests
srvx
and random port for remote provider (#31432)🤖 CI
❤️ Contributors
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](https://redirect.github.com/nConfiguration
📅 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.