-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Kit builds my project two times even if I disabled ssr #2937
Comments
Since there's no more |
I've found myself wanting the same thing. We have a desktop app that uses a bunch of svelte pages. I've been investigating a switch to sveltekit+static adaptor, but the build time is a bit painful: around 10 seconds for the client, and another 10 for the server. Being able to shave it by half would be a noticeable improvement. Why not just use "dev" instead of "build"? When actively working on a page, we would. But the app has its own build system, which builds all oudated components, and for sveltekit we'd need to invoke a build. If it's practical to cut out the SSR step / approximately halve build time, I would be willing to get my company to sponsor a sveltejs dev who was willing to implement it. If interested, please email d-svelte at ankiweb.net. |
I'm in the same boat, I'm never going to use ssr. |
Same, would just like to have a flag where server build is off, could resort to just SvelteJS with a random router, but I like the SvelteKit structure |
I'm using SvelteKit, but with a Flask backend. I have no use for the server part of SvelteKit; I only want to use the routing. The additional build takes extra time and is noisy (since I don't use it). Please enable us to disable it. IMO the routing and server functionality shouldn't be coupled. It makes SvelteKit less desirable if it's all-or-nothing. |
Describe the bug
I couldn't understand why Kit builds my project two times even if I disabled
ssr
in svelte.config.cjs:Reproduction
https://github.com/frederikhors/iss-svelte-kit-tailwind-comments
Logs
System Info
Severity
serious, but I can work around it
The text was updated successfully, but these errors were encountered: