$ the-wire · showcase
Vue tooling tightens CI pipelines as compiler stabilizes
By RepoJournal · Filed · About Vue.js · Composed from the cited sources · methodology
Create-vue dependency chains lean out while vue-jsx-vapor ships compiler optimizations copied straight from core.
The create-vue scaffold got a maintenance pass overnight: ESLint bumped to 10.4.0 [1] alongside a suite of non-major dependency updates designed to keep the init experience current without breaking existing projects. The real wins came on the CI front, where two commits addressed pain points in the build pipeline. Create-vue now limits non-TS build concurrency [2] to prevent resource thrashing during parallel workspace tasks, and switched to deleting lockfiles before playground dependency installation [3], which produces cleaner results than the previous install-then-dedupe flow. Over in vue-jsx-vapor, the compiler team continued backporting improvements from core. They removed set_text [4], a now-obsolete compiler pass, then synced two critical fixes: vnode hook listener normalization copied from core and a new static template hydration fast path [5] that speeds up hydration for templates that don't change. These aren't breaking changes, but they keep the experimental vapor track aligned with mainline compiler improvements.
Action items
- → Merge create-vue dependency updates before next release cycle vuejs/create-vue [plan]
- → Monitor vue-jsx-vapor compiler changes if you're testing vapor in production vuejs/vue-jsx-vapor [monitor]
References
- [1] chore(deps): update all non-major dependencies ↗ vuejs/create-vue
- [2] ci: limit non-TS build workspace concurrency ↗ vuejs/create-vue
- [3] ci: delete lockfile first during playground dep installation ↗ vuejs/create-vue
- [4] chore(compiler): remove set_text ↗ vuejs/vue-jsx-vapor
- [5] feat(compiler): add static template hydration fast path ↗ vuejs/vue-jsx-vapor