Instance vs Global State with composable functions and the Composition API

Introduction to Filip, VueStorefront, early adoption of the Composition API, and our example app

4:56

BONUS - Vue 2 Composition API plugin vs Vue 3 Composition API implementation

4:20

Why We Need Reactivity

1:59

Ref and Reactive - key parts of the Composition API's Reactivity System

6:21

BONUS - Vue 2 'gotcha' with pulling functions out of setup

2:34

Composition API

5:04

Instance vs Global State with composable functions and the Composition API

5:08

Async Fetch Composable Function (example)

5:54

Composition API in VueStorefront Source Code

8:13

BONUS - How VueStorefront Next is Organized (overview)

11:10

0% done with Expert Series - Filip Rakowski - Composition API in VueStorefront

5:08 | Published on 5/7/2020 |
|

Instance vs Global State with composable functions and the Composition API

If we use our composable function in multiple places, why doesn't the data carry over?

Each use of the composable function creates a new instance of all the data... unless the data is defined outside the function.

What do others think of VueScreencasts?

"great 👍"

—Paul Hacker

"As always thanks for the great content."

—Paurakh Sharma Humagain

"Damn it's good content. I am happy that I found VueScreencasts."

—Shamim Hossain

"Great tips great video thanks"

—Happyoe