$ the-wire · showcase
VUE LANGUAGE TOOLS PATCHES CLASS AND STYLE HANDLING
By RepoJournal · Filed · About Vue.js · Composed from the cited sources · methodology
1 person shipped this
Vue's TypeScript plugin now correctly treats `class` and `style` as non-boolean properties, fixing a persistent type inference bug that affected template compilation.
The fix ships in v3.3.3 [2], which landed overnight and addresses issue #6080 where the language tools incorrectly flagged `class` and `style` bindings as boolean properties [1]. This wasn't just a type-checking annoyance - it broke autocomplete and forced developers to work around false positive errors in their templates. The same release also patches a grammar scopes leakage in capitalized tags [2] that was bleeding Vue syntax highlighting into unrelated code blocks, and restores TypeScript's auto-import behavior inside Vue files [2], which had regressed in the previous version. The team also hardened the auto-version workflow against environment variable injection attacks [2], a small but critical security fix for automation pipelines. v3.3.3 is a solid maintenance release that clears out accumulated friction points.
Action items
- → Upgrade @vue/language-server to 3.3.3 if you're seeing false boolean property errors on class/style bindings vuejs/language-tools [plan]
- → Update VSCode extension to latest if autocomplete has been sluggish in Vue files vuejs/language-tools [monitor]
References
- [1] fix(typescript-plugin): do not treat `class` and `style` as a boolean property ↗ vuejs/language-tools
- [2] v3.3.3 ↗ vuejs/language-tools
