How we do Vue: one year later

What this post added

This post details GitLab's experience and best practices for using Vue.js one year after adopting it. Key technical contributions include: advocating for VueX for state management in medium to large features, emphasizing the importance of writing high-quality, maintainable, and performant Vue code by following documentation and avoiding unnecessary reactivity; strongly advising against mixing jQuery with Vue.js, proposing server-side data provision as a better alternative for DOM querying; and outlining the structure of a proper Vue app with a single store, service, and entry point, passing server-built URLs via data attributes. Performance improvements are highlighted through the refactoring of issue comments from Haml/jQuery/Rails to Vue.js, leading to faster page loads and reduced jank by addressing issues with event listeners and asynchronous loading.