Vue tooling absorbs Vue 3.6, VitePress rebuilds on tsdown

The week's most substantial move was VitePress migrating its build to tsdown [1], a change that reworks how the documentation tool compiles and packages itself. This is infrastructure work with wide surface area: it lands alongside a redesigned navbar [2], relocatable builds, and CSP-related theme fixes [4]. [3] removes unused icons as part of a codebase format sweep. For VitePress users, the practical takeaway is that the next release will carry a different build pipeline and a changed default theme look, with no API breakage called out in the changelog.

Over in Vue language tools, the team adopted the Vue 3.6 API surface [7], unwrapping setup bindings by value so template bindings can be called without .value [8]. The same release eliminates unmapped codegen diagnostics [9], closing a silent type-check gap that previously let type errors slip through when codegen output didn't map back to source. reduces focus mode overhead, trimming work the language server does when a file isn't in focus.

Vue core shipped a batch of correctness fixes [10][11][12][13]. Map and Set values are now compared correctly during reactivity, the Suspense fallback logic no longer misidentifies a leaving branch, and v-model re-syncs a select when its model is overridden in a change handler. These are targeted, non-breaking patches but they close real edge cases in reactivity and form handling.

Finally, VitePress un-deprecated Theme.setup and now composes it across extends [5], restoring a documented extension point. The fix also introduced --vp-local-nav-divider-color [6] for theme customization.

The week wraps a period of consolidation rather than feature landings. Tooling adopters should test their builds against the new VitePress beta and Vue language tools release once they publish, since build and diagnostics behavior both changed.