OverviewIntroductionVue TourReact Tour🌱 Get StartedScaffold new appAdd to existing app📚 GuidesBasicsRoutingData FetchingPre-rendering (SSG)Access pageContext anywhereMore<head>Static Directory (public/)Hydration MismatchSPA, SSR, SSG, HTML-only.env FilesInternationalization (i18n)File StructurePaths AliasesHTML StreamingAPI RoutesClient-only ComponentsDynamic import()Error TrackingDebugVitevite-plugin-ssrRender-as-you-Fetch
RoutingServer Routing VS Client RoutingFilesystem RoutingRoute StringRoute FunctionActive LinksPage RedirectionBase URLCatch-All RoutesNested RoutesVue Router & React Router🔌 IntegrationData fetchingApollo (GraphQL)Vue QueryRelay (GraphQL)Wildcard API (RPC)urql (GraphQL)gRPC (RPC)OtherData storeVuexReduxPullStateOtherAuthenticationNextAuth.jsOtherCSS, styling, CSS frameworksTailwind CSS / Windi CSSVuetifyCSS-in-JSstyled-componentsBoostrap (Vanilla JS)Sass / Less / StylusOtherUI frameworksSveltePreactSolidOtherOtherMarkdownHTTPSOther🌍 DeployStatic hostsGitHub PagesCloudflare PagesNetlifyOtherServerlessCloudflare WorkersVercelAWS LambdaFirebaseOtherDockerOther⚙ APINode.js & browserpageContext.page.js • export { Page } • export { onBeforeRender }Node.js.page.server.js • export { onBeforeRender } • export { passToClient } • export { render } • export { prerender } • export { doNotPrerender }escapeInjectBrowser.page.client.jsgetPage()useClientRouter()navigate()Routing.page.route.js_default.page.route.js • filesystemRoutingRoot • onBeforeRouteSpecial pages_default.page.*_error.page.jsIntegrationcreatePageRenderer()Vite PluginCLICommand prerenderDebug
Vite
To enable Vite's debug logs, we set the environment variable DEBUG to vite:*.
$ DEBUG=vite* npm run devIf you want the same functionality for
vite-plugin-ssr, upvote and/or comment the feature request #249.
We recommend directly inspecting Vite's built source code in node_modules/vite/, for example by injecting console.log() calls to bisect down the bug.
It may sound scary to dig into Vite's source code, but it's often a faster (and a more interesting) way to find the root cause of problems. Vite's source code is well written and pleasurable to read. It also get's you closer to actually being able to fix the problem. If you open a Vite PR, feel free to reach out to the
vite-plugin-ssrmaintainers to get your PR merged quicker.
vite-plugin-ssr
Reach out to the vite-plugin-ssr maintainers if you believe to have found a bug that has its root cause in vite-plugin-ssr's source code.