FRONTEND
Nuxt v4.4.3
RESUMEN
> 4.4.3 is the next patch release. v4.4.4 was published with no changes due to an issue running the release script for v4.4.3. 👉 Changelog compare changes 🔥 Performance - nitro: Directly import nuxt package version ([#34567
Descripción Detallada
> 4.4.3 is the next patch release. v4.4.4 was published with no changes due to an issue running the release script for v4.4.3. 👉 Changelog compare changes 🔥 Performance - nitro: Directly import nuxt package version - vite,webpack: Use vfs for manifest + vite node server - nuxt: Clean-up build hooks + emit gc'd snapshots - nuxt: Skip key watcher when useAsyncData key is static - kit: Parallelise module load + cache jiti instances - nuxt: Batch-resolve typescript hoist paths with cached base roots 🩹 Fixes - nuxt: Handle negative zero in getUserTrace slice boundary - nuxt: Signal error state and clear timers in loading indicator cleanup - nuxt: Fix broken hook cleanup in route announcer - nuxt: Filter `clearNuxtState` key enumeration by useState prefix - nuxt: Correct `useFetch` `cache` options type ((
Explicación con IA
Genera un resumen en lenguaje claro de los cambios de este release.
Releases Relacionados
FRONTEND
Nuxt v3.21.3
> 3.21.3 is the next patch release. v3.21.4 was published with no changes due to an issue running the release script for v3.21.3. ## 👉 Changelog [compare changes](https://github.com/nuxt/nuxt/compare/v3.21.2...v3.21.3) ### 🔥 Performance - **nuxt:** Batch-resolve typescript hoist paths with
FRONTEND
Nuxt v4.4.0
> 4.4.0/4.4.2 is the next minor release (v4.4.2 was published with no changes due to a publishing failure) ## 👀 Highlights ### 🏭 `createUseFetch` and `createUseAsyncData` You can now create **custom instances** of `useFetch` and `useAsyncData` with your own default options ([#32300](https