Vue's monthly grind: tooling stability and VitePress rewrites mark August

In August, the Vue umbrella releases centered on incremental improvements across core and its ecosystem. Vue itself remained on the 3.5 line, with 3.5.41 shipping in early August [1], while the first candidate for 3.6 (3.6.0-RC.3) landed mid-month, aimed primarily at TypeScript tooling fixes . By month's end, language-tools aligned its internals with the upcoming 3.6 API , but the framework itself never advanced to a final 3.6 release during the period. Also of note, VitePress entered alpha 19 with a substantial inclusion rewrite.

Language-tools, the umbrella for the Vue language server and extensions, saw several releases in August, most notably v3.3.9 [2] and v3.3.10 [3], addressing template type fixes and further stabilizing the tool as the core RC progressed. Language-tools also adopted the upcoming Vue 3.6 API by dogfooding an experimental TypeScript native bridge (typescript-native-bridge@6.0.3-bridge.8.tsgo.7.0.2) [4], a move that likely improves performance and maintainability ahead of Vue 3.6's release. Across the ecosystem, other repos focused on small fixes: test-utils updated docs for v-model testing and added a global configuration option for plugins [5][6], while @vue/apollo-composable fixed a reactivity trap by preserving DocumentNode identity across its composables [7].

VitePress shipped a major rewrite of code snippet and markdown inclusion, plus a separate breaking feature that rebases relative URLs in included files [8][9]. It also received several functional patches: fix for list spacing [8] was covered elsewhere, but the theme overhaul introduced severity colors, and the alpha state carries implications for adoption. VitePress continued its tooling modernization, moving its build to tsdown and shipping relocatable builds by month's end . VitePress also eagerly resolves $frontmatter expressions , improving dynamic content handling, and improved tooling elsewhere with a fix for silent type-checking gaps in Vue tooling , though the underlying source links are absent.

In the surrounding tooling, Vue's native toolchain (create-vue) updated its dependencies, including jsdom to v30 [10] and released a dependency refresh across its tooling [11]. VitePress fixed theme issues and CSP and icon builds , while Vue Router stopped resolving on every navigation [12] and fixed query parameter inheritance [7]. Vue's Playground pinned TypeScript 6 after TypeScript 7 broke type support [9], and jsx-vapor shipped a breaking beta that drops CJS support and focuses on type inference [13]. The cumulative effect: August brought no framework-breaking shifts but a steady supply of stability and feature work across the core and satellite projects.

For those depending on the Vue core, the story is one of continuity: 3.5 remains the stable line, while 3.6 is clearly in an extensive RC phase. If you build tools that rely on language-tools or VitePress, expect continued churn as those projects modernize. The ecosystem is moving toward better performance via native bridges and more robust build systems, but no changes here demand immediate adoption for most users.