Change Details

From parent task: > Setup (add Vue.js as a dependency in our extension.json, install Vue dev tools for testing, make sure linting works with the new code, etc.) > Architecture proof of concept (decide and test what's the best way to "plug" Vue.js, create a main app or several, etc)

From parent task: > Setup (add Vue.js as a dependency in our extension.json, install Vue dev tools for testing, make sure linting works with the new code, etc.) > Architecture proof of concept (decide and test what's the best way to "plug" Vue.js, create a main app or several, etc) Since adding Vue as a dependency is a module specific configuration rather than project-wide, module-agnostic requirements for this task fit better. We can add Vue and other dependencies like Codex per module once we start migrating them. Scaffolding in a generic way is complicated for the variety of UI and modules we have. See related task {T297763} for a module proof of concept. Growth Experiments Vue global settings: [x] Jest test framework setup [] Lint rules updates if needed

From parent task: > Setup (add Vue.js as a dependency in our extension.json, install Vue dev tools for testing, make sure linting works with the new code, etc.) > Architecture proof of concept (decide and test what's the best way to "plug" Vue.js, create a main app or several, etc) Since adding Vue as a dependency is a module specific configuration rather than project-wide, module-agnostic requirements for this task fit better. We can add Vue and other dependencies like Codex per module once we start migrating them. Scaffolding in a generic way is complicated for the variety of UI and modules we have. See related task {T297763} for a module proof of concept. Growth Experiments Vue global settings: [x] Jest test framework setup [] Lint rules updates if needed