I'll be speaking at v-conf Taiwan 2026 about Vue Language Tools, come join us! Get your early bird ticket with discount code "SERKO100" 👇

vue-jsx 3.3.0-rc.1 is out 🚀. A new package: vue-jsx, formerly vue-jsx-vapor — Big thanks to bravf on GitHub for gifting me the npm name! 1. Virtual DOM by default, Vapor Mode opt-in 2. Native type inference for `ref` (exposed) and `slots` 3. ESM only vuejsx.dev

Introducing Bolt Forge. Free until Oct 14th: - Up to 50x more usage - The new frontier: GLM, DeepSeek, Kimi - Zero usage charges Live now in your model picker on bolt.new And one more thing... 👇

oxlint + oxfmt might be the best thing that happened to javascript tooling if you're still using eslint + prettier in 2026, i'm genuinely concerned

I previously said Volar and tsslint would never get another major version bump, but thanks to TS 7.1's Content Mappers, we'll have to release: * Volar.js v3 * Vue Language Tools v4 * tsslint v4

How bad is my English? I can spell "reproduction," not because I remember how it's spelled, but because my fingers remember the typing sequence for each letter.

Just dropped TNB into vuejs/language-tools. vue-tsc → 2.7x faster tsslint → 2x faster

Introducing typescript-native-bridge. Native TS performance in the tools you already use. Dropped in one package override, and vue-tsc got ~3.3× faster while using 45% less memory. Works with astro-check, svelte-check, glint, tsslint, tsserver, @mdx-js/typescript-plugin. No new CLI or LSP needed. github.com/johnsoncodehk/typ…

The next version of Vue language tools will support v-directives in Vapor mode (Vue 3.6+) 🎉 I help implement it as a contributor, thanks to @KazariEX_0929 for reviewing ☺️ github.com/vuejs/language-to…

I feel like we are on one of those pendulum swings right now where people undo a decades worth of work only to realize in 5 years they over swung because they missed the actual problem. We see this all the time. I'm not going to argue against imperative handles in all cases. But I want you think about the implications. If you unwind these things you remove guarentees. Like why do developers like Rust or TS? Its because through constraints certain classifications of issues aren't possible. The solution solves itself structurally. Structural constraints also have a nice property when composed. You keep benefitting from them as you layer on complexity. Build more constrained systems. Like if you aren't batching synchronous updates you probably have no foundation to managing async race conditions structurally. We shouldn't confuse incidental simplification(removing a problem) with structural simplification. Sometimes legitimately we don't need to solve certain things. The solution should fit the problem. But more often than not in a well established space we are just delaying the inevitable.

Volar now has first-class support in tsdown and rolldown-plugin-dts. It can generate `.d.ts` files for all file types supported by Volar, including Vue and Astro. github.com/sxzz/rolldown-plu…

The wait is over – @AnthropicAI’s Claude Fable 5 is back! Try it in JetBrains AI Assistant, Junie, and Air today. What are you going to build?

Goodbye Claude 👋 But thank you for letting me try.

Opinions along this line show a clear disconnect between those who use React only vs. those who don’t use React at all. It’s easy to assume what makes sense for you makes sense for everyone because who cares about those who don’t use the same framework as mine? But - Vite is framework agnostic, vendor agnostic, and we can’t go down that slippery slope. What if tomorrow we are going to add another 5mb for a Rust Vue compiler, and next week another for Svelte, Solid, and Astro? One can argue React is the most popular so it deserves special treatment, but where should that line be drawn? Why NOT other frameworks? Vite is downloaded 12 millions a week, every uncached download consumes bandwidth and CI time. 5mb might not mean much for an individual end user, but it can result in meaningful difference at scale. If there is a way to optimize it, we should try that. It’s ironic that people complain about node_modules size while at the same time dismissing size optimization efforts.

Happy to announce vue-tui@0.1! What you get: - Vue <script setup> + reactivity, rendered to the terminal - Real Yoga flexbox layout (Box / Text) - React Ink's battle-tested patterns — now in Vue - Kitty keyboard protocol, bracketed paste, animation, screen-reader a11y Public beta, seeking feedback

⚡️ Announcement for Vize Vize is entering the Real World Testing phase. vizejs.dev/blog/notes/2026-0… Looking for: ・Bug reports (Issues) ・Pull Requests ・Medium-to-large Vue projects to test against The next milestone is v1.0.0-alpha.

These past few months, I've been thinking about my role in OSS in the age of AI. AI amplifies a good developer's output by 10x — but in the hands of a bad developer, it's the AI's hallucinations that get amplified by 10x. Solid programming skills and taste remain essential — and a good developer's attention is a precious asset in itself. Since coding ability and time are no longer the main bottlenecks, I believe we should channel these strengths — with the help of AI — into solving the problems that have gone unsolved simply because they aren't "fun," but that can still genuinely make the world a little better. If we get this right, I think the OSS community could shift from being bottlenecked by manpower to being bottlenecked only by courage and care.