$ the-wire · showcase
LANGUAGE-TOOLS V3.3.2 SHIPS WITH V-FOR TYPE PRESERVATION
By RepoJournal · Filed · About Vue.js · Composed from the cited sources · methodology
2 people shipped this
Vue's TypeScript tooling now preserves literal types in inline v-for loops, fixing slot detection in component documentation generation.
Language-tools v3.3.2 [1] lands a critical fix for developers using vue-component-meta to generate component docs. The release preserves literal types for inline v-for sources [2], solving a long-standing issue where arrays typed as unions (like string | number[]) would lose enumerable property information in mapped types, preventing slot detection inside loops [3]. The vscode extension gets its own improvements in this drop, including tsserver content transformation [4] and a fix for trailing slashes in capitalized self-closing tags that were incorrectly flagged as invalid. On the maintenance front, the team added tinyexec@1.2.2 to the supply chain policy exclude list [5], and updated the lock threads CI action across vitepress [6]. If you're shipping component documentation or relying on precise type inference in template loops, this upgrade moves from optional to necessary.
Action items
- → Update language-tools to v3.3.2 if you use vue-component-meta for documentation vuejs/language-tools [plan]
- → Update vscode extension for tsserver and template validation fixes vuejs/language-tools [plan]
References
- [1] v3.3.2 ↗ vuejs/language-tools
- [2] feat(language-core): preserve literal types for inline `v-for` sources (#6067) ↗ vuejs/language-tools
- [3] feat(language-core): preserve literal types for inline `v-for` sources ↗ vuejs/language-tools
- [4] v3.3.2 ↗ vuejs/language-tools
- [5] chore: add `tinyexec@1.2.2` to truct policy exclude list ↗ vuejs/language-tools
- [6] ci: update lock threads action ↗ vuejs/vitepress
