ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Vue Storefront's default client-side rendering hurts LCP and SEO. Adding Nuxt 3 SSR streams fully formed HTML from the server, reusing existing GraphQL composables. A minimal config, static generation for catalog pages, and the memory/hydration trade-offs you'll actually hit.
Use Nuxt 3 server routes as a Backend-for-Frontend (BFF) to hide API secrets, aggregate data, and reduce client-side complexity without needing a separate backend service.
Design pattern for Nuxt 3 server routes with Nitro, covering trust boundaries, runtimeConfig separation, operational checks, and when to scale beyond co-location.
Vue Storefront 2 replaces a monolithic store with granular composables like useCart and useProduct. The pattern decouples UI from commerce backends via a middleware layer, enables SSR prefetching and typed state, with trade-offs around over-fetching and middleware scaling.
Render initial HTML on the server with Nuxt 3, prefetch data with useFetch and useAsyncData, and isolate browser-only code to avoid hydration mismatches and duplicate requests.
Learn how to turn a Nuxt 3 app into a single Nitro‑powered serverless function, the minimal design, trust boundaries, operational checks, and when to re‑architect.
An architecture note on server-rendering VueStorefront product pages with Nuxt 3: one dynamic route, one server‑side fetch, slug validation, ISR caching, and the checks that prove SSR is actually happening.
Nuxt 3's Nitro server engine provides a unified runtime for deploying across serverless platforms like Vercel and Cloudflare Workers, with a single entry point and clean configuration boundaries.
Learn how to leverage Vuestorefront's server‑side rendering with Nuxt 3's useAsyncData to fetch product data reliably, see a minimal setup, and avoid common pitfalls.
nuxt
vuestorefront