Vue JS Best Practices
summary
Claims concrete results: GitLab runs Vue in production for more than a year, refactors legacy features and adds new ones using Vuex for state management, replaces DOM hacks with data-driven updates, and composes pages from multiple smart components (five merge-request widgets on one page). Uses single-file components with scoped CSS, measures hotspots with Vue perf tools, and notes Vue is 20 KB minified and gzipped and integrates with Sentry for runtime error tracking.
AI-written summary · about
chapters (12)
- 0:00Intro
- 1:22About Vue
- 2:31About Github
- 3:04About GitLab
- 4:13Why Vue JS
- 6:51Vue best practices
- 7:41Vue datadriven framework
- 10:38Computed properties
- 13:00Scope CSS
- 15:33Performance
- 16:17Common Component Communication
- 19:29React
related talks
27mVue and Vuex: The good, the bad and the ugly
31mHow do we use Vue js in GitLab
20mVueJS at
27mHow We Do Vue At GitLab
39mVue.js - developer friendly, fast and versatile
47mVue & Vuex
49mVue and Vuex: Structure your app with centralized state management
26mMigrating a big old codebase to Vue 3: what I'm excited about
