$ the-wire · showcase
Static boolean bindings fixed in Vue's DOM compiler
By RepoJournal · Filed · About Vue.js · Composed from the cited sources · methodology
Vue's compiler-dom now keeps literal boolean bindings intact in static content, and eslint-plugin-vue stops crashing on type assertions it never expected.
fix(compiler-dom): preserve static boolean binding semantics vuejs/core
edison1105's compiler-dom patch makes static boolean bindings behave like their runtime equivalents: false-like values are now omitted from the rendered output, while truthy and string values are preserved. Bound boolean attributes on custom elements keep their runtime behavior instead of being stringified. The fix closes three tracked reports (#16051, #15910, #16053) and has already landed as ...
fix(require-explicit-slots): don't crash on non-`SlotsType` type assertions vuejs/eslint-plugin-vue
The vue/require-explicit-slots rule used to throw "Cannot read properties of undefined (reading 'name')" on any slots option whose type assertion was not a type reference, e.g. slots: {} as any, because it read typeAnnotation.typeName.name unconditionally. It now skips keyword and literal type assertions instead of aborting the lint run.
Reuse util functions vuejs/eslint-plugin-vue
FloEdelmann consolidated duplicated helper code in eslint-plugin-vue onto shared util functions, a cleanup with no rule behavior changes attached. The same commit is what the plugin's release branch picked up.
Update dependencies vuejs/eslint-plugin-vue
The plugin's dependencies were bumped in a separate maintenance pass, keeping the lint toolchain current without touching rule logic.
chore(deps): update aligned oxlint packages to ~1.90.0 vuejs/create-vue
The long tail: create-vue's Renovate queue moved eslint-plugin-oxlint from ~1.88.0 to ~1.90.0 and oxfmt from ^0.73.0 to ^0.75.0, routine bumps for scaffolds generated by the template.
