sveltejs / sapper

The next small thing in web development, powered by Svelte
https://sapper.svelte.dev
MIT License
7k stars 434 forks source link

build option to keep destination #1703

Open ayyash opened 3 years ago

ayyash commented 3 years ago

Currently with sapper build the destination is cleared out before building the server and client folders, that makes my life too hard, because I want to create static server files that serve a lot more than just the svelte app, it would be nice to at least do one of those two things:

Florian-Schoenherr commented 3 years ago

Can't you put the build output files in their seperate folder and reference them another way? I would generally never mix build outputs or something like that. If you reference anything else, wouldn't you need to modify the html's after every build? Honestly just trying to understand what you want to do, no offense! 😄

ayyash commented 3 years ago

im not trying to mix, im trying to run sapper output files from my own nodejs server, which runs other things, like for example a middleware to get country code, that is used for sapper website AND some other admin site using another technology... for example? i mean this is a simple scenario, I ran into much more in the past that compelled me to separate code generated from the server that runs it. im not trying to mess with the output files themselves.