ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
When using Nuxt 3 with the Nitro engine, server-side requests initiated via useFetch rely on the Node.js runtime for certificate validation rather than the client's browser. While client-side requests utilize standard trust stores, the SSR process often fails when targeting internal APIs protected by private CAs. There is currently uncertainty regarding how
Context Vue Storefront 2.10+ composables such as useProduct and useCategory cache responses in Pinia stores keyed by normalized parameters. During SSR, the @vue-storefront/nuxt module serializes Pinia state, but client-side hydration recomputes cache keys using runtime parameters—including locale, currency, and custom headers—that may not match the SSR conte
The goal is to determine whether a single component that fails to hydrate in an Astro application causes the entire page to lose interactivity when the project is built with output: server instead of output: static. In static builds, hydration mismatches are rare because there is no client‑side JavaScript, but SSR introduces a boundary where environment‑depe
Goal: Ensure that data fetching in Nuxt 3 handles both navigation‑initiated cancellation and request timeouts uniformly, especially during server‑side rendering where no client‑side AbortSignal is available. Currently, useFetch automatically forwards an AbortSignal when the navigating component is destroyed, but it does not apply a default timeout; during SS
The useMediaQuery hook reads breakpoints from the theme and relies on window.matchMedia , which is absent during server‑side rendering. Without a custom ssrMatchMedia function supplied via the theme, the hook defaults to false , often causing hydration mismatches in frameworks like Next.js. The MUI team has discussed adding a built‑in ssrMatchMedia implement
vuestorefront
astro