Version Details and Security Vulnerabilities

📦

@nuxt/schema

3.14.0

Comparision Betweeen 3.14.0 and 3.13.2

Identify the differences between the current version of the package and the previous one.

Version

Dependencies

Dev Dependencies

Peer Dependencies

Distributed Files

Unpacked Size

575.89 KB

566.73 KB

Version 3.14.0 Details

@nuxt/schema version 3.14.0 introduces several notable updates compared to the previous stable release, 3.13.2, impacting both dependencies and development dependencies. Key dependency upgrades include c12 (from 1.11.2 to ^2.0.1), unimport (from 3.12.0 to 3.13.1), and pkg-types (from 1.2.0 to ^1.2.1), suggesting improvements in configuration handling, module resolution, and type definition management. The update to c12 is particularly significant as it likely brings enhanced configuration merging and overrides.

Significant changes also appear in the development dependencies, reflecting advancements in the Nuxt development environment. Core updates involve vue (from 3.5.5 to 3.5.12), vite (from 5.4.5 to 5.4.10), h3 (from 1.12.0 to 1.13.0), @unhead/schema (from 1.11.5 to 1.11.11), @vue/compiler-sfc (from 3.5.5 to 3.5.12), @vue/compiler-core (from 3.5.5 to 3.5.12), and @vue/language-core (from 2.1.6 to 2.1.10). These updates indicate refinements and bug fixes in Vue 3 compilation, build tooling, server-side rendering capabilities, and schema definitions for meta tags. The increased versions of @vitejs/plugin-vue mean a bump from 5.1.3 to 5.1.4 These cumulative updates suggest a more optimized and reliable development experience for Nuxt 3 users, particularly concerning performance and type safety. Developers are encouraged to upgrade to version 3.14.0 to leverage these enhancements and maintain compatibility with the latest Nuxt ecosystem improvements.

Security Vulnerabilities

This site is an independent open-source project and is not affiliated with, endorsed by, or sponsored by npm, Inc. or GitHub, Inc. The name “npm” is a registered trademark of npm, Inc., used here solely to describe compatibility and reference publicly available npm package data.