How We Updated @vue/test-utils in GitLab
summary
A developer describes updating the @vue/test-utils library inside GitLab: the work required sending over a dozen pull requests to @vue/test-utils, proposing an internal RFC to create a fork, and digging into Vue’s reactivity internals. The talk focuses on the practical problems encountered—coordination with upstream, maintaining code and test quality—and the approaches used to get the updates merged and stable in GitLab.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 4:25Goals for @vue/test-utils update
- 9:45Vue basics
- 11:34@vue/test-utils in GitLab
- 14:05Component testing problems
- 21:30Evan You's role
- 22:37Shallow vs deep render
- 28:04Slot testing challenges
- 32:47Vue 3 migration issues
- 39:33DOM mounting specifics
- 42:51Open Source responsibility
- 47:50Key @vue/test-utils changes
- 51:50Fixes for destroyed components
- 53:15Props infinite loops
- 1:01:30Rewriting from scratch?
- 1:05:10Summary
related talks
27mHow We Do Vue At GitLab
25mThe Future of Vue's Test Utils
31mHow do we use Vue js in GitLab
27mVue and Vuex: The good, the bad and the ugly
29mMigration of GitLab Codebase from Vue 2 to Vue 3
25mPanel With the Core Committers
39m7 ways to make your Vue unit tests better
26mMigrating a big old codebase to Vue 3: what I'm excited about
