How we used Nuxt and Composition API in Vue Storefront?
summary
Claim: a full rewrite of Vue Storefront onto Nuxt plus the Composition API turns a monolith into domain-oriented independent packages, eliminates the need for Vuex for most e‑commerce cases, and ships composables as the public API. Built: Vue Storefront Next, many composable packages, and a sharedRef workaround for Nuxt SSR because the Nuxt Composition API module injects keys. Result: production rollout with caveats and extra workarounds but overall no Vuex needed and much simpler modular code.
AI-written summary · about
chapters (20)
- 0:00Intro
- 0:52What is Storefront
- 3:22What is Composition API
- 5:14Composition API benefits
- 5:54Component level
- 12:22Composition API
- 14:32Vue Storefront
- 19:59Why use Composition API
- 22:23Solution
- 23:28Shared State
- 25:21Conclusion
- 25:58Questions
- 26:46Why not use Nuxt
- 28:19Modularization
- 29:54Mindset
- 32:12Never modify tools internals
- 36:06repositories
- 37:06best practices
- 40:27style guide
- 41:46split smart and dump components
related talks
36mThe biggest eCommerce Vue project with Composition API
23mMaking eCommerce sexy again with Vue Storefront and Composition API
46mNuxt.js and the Composition API
30mOpen Source eCommerce with Nuxt and Vue Storefront
22mIntroduction to Vue Storefront Next
30mImplementing an eCommerce online shop in no time using a boilerplate approach
21mHow to enable large scale collaboration between disciplines using Nuxt
22mWays to architecture your vue/nuxt app
