yarn install
yarn run serve
yarn run build
This project is using Vue Composition API (inspired by React Hooks) with Vuex and Vue Router.
Vue Composition API is becoming the preferred way of creating components in upcoming Vue@3. It's ported to Vue@2 using "Vue2 plugin for the Composition API".
The main motivation of using this approach is to utilize fantastic logic reuse & code organization. After initial adjustment to new way of component definition it becomes obvious that it's easier to grasp component's logic as it's clearly separated from unrelated code (as opposed to previous data/computed/methods separation).
How "Options API" (current standard) compares to "Composition API"? Here's example how business logic can be distributed in component's code in both approaches:
