FRONTEND
Nuxt v3.21.3
RESUMEN
> 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 🔥 Performance - nuxt: Batch-resolve typescript hoist paths with
Descripción Detallada
> 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 🔥 Performance - nuxt: Batch-resolve typescript hoist paths with cached base roots - vite,webpack: Use vfs for manifest + vite node server 🩹 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 - nuxt: Prevent in-flight requests from overwriting cleared async data - nuxt: Check response status before parsing payload - nuxt: Handle TS type assertions on member expression callees in keyed functions parser - nitro: Resolve h3 export pa
Actualización de Nuxt v3.21.3 con cambios de rendimiento y correcciones, pero es breaking.
- Mejora en el rendimiento al resolver rutas de TypeScript con raíces base en caché.
- Uso de vfs para el manifiesto y servidor de nodo de vite.
- Correcciones en el manejo de errores y limpieza de hooks.
A quién le importa
Solo si usas Nuxt y necesitas mantener la compatibilidad.
Generado por IA · puede contener errores
Releases Relacionados
FRONTEND
Nuxt v4.4.3
> 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](https://github.com/nuxt/nuxt/compare/v4.4.2...v4.4.3) ### 🔥 Performance - **nitro:** Directly import nuxt package version ([#34567
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