Support SvelteKit with Static Adapter for SPA Client-Only Applications

Author: ahmdsbCreated May 25, 2026Updated Jul 11, 2026

Is your feature request related to a problem? Please describe.

Currently, the repository does not officially support SvelteKit projects, especially those using @sveltejs/adapter-static.

For client-only SPA applications, using a static adapter is often preferred because it allows the app to be deployed easily on static hosting providers without requiring a Node.js server runtime.

In addition, SvelteKit already provides a built-in routing system, making it more convenient compared to setting up routing manually in plain Svelte projects.

Describe the solution you'd like

Add official support for SvelteKit, including compatibility with @sveltejs/adapter-static.

The integration should work properly in SPA client-only environments and support static builds generated by SvelteKit.

It would also be helpful to provide:

  • Documentation for SvelteKit setup
  • Example project using adapter-static
  • SPA fallback configuration guidance

Describe alternatives you've considered

Using plain Svelte with external routing libraries is possible, but SvelteKit already provides built-in routing and project structure out of the box.

Another workaround is manually configuring the integration in SvelteKit projects, but this requires additional setup and may not work consistently across different configurations.

Additional context

Static deployment support is useful for platforms such as GitHub Pages, Netlify, Cloudflare Pages, or other static hosting providers.

Source: jasontaylordev/CleanArchitecture