-
-
Notifications
You must be signed in to change notification settings - Fork 2k
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
svelte-kit build
should respect vite.build.emptyOutDir
#1044
Labels
feature / enhancement
New feature or request
Comments
Duplicate of #1039 |
@benmccann did the fix for #1039 handle rebuild if a file has been removed? I experienced it locally (with version next.89, not sure when that went out) when I removed a .svelte route, the generated html file was still present in build. |
This is still an issue with the latest. Seems like it needs to be an update to adapter-static. Recreation (for me):
Requesting a reopen. |
babichjacob
changed the title
Svelte Kit not emptying build directory
SvelteKit should respect vite.build.emptyOutDir
May 3, 2021
babichjacob
changed the title
SvelteKit should respect vite.build.emptyOutDir
SvelteKit should respect May 3, 2021
vite.build.emptyOutDir
babichjacob
changed the title
SvelteKit should respect
May 3, 2021
vite.build.emptyOutDir
svelte-kit build
should respect vite.build.emptyOutDir
Greenheart
added a commit
to Greenheart/greenheart.github.io
that referenced
this issue
Jul 30, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
Building using
adapter-static
, files from the previous build are still in the build folder after a subsequent build. Vite has abuild.emptyOutDir: true
default that svelte-kit seems to ignore.Describe the solution you'd like
It would be nice if svelte-kit cleared the build directory, to avoid the build folder ballooning in size when doing multiple local builds.
Describe alternatives you've considered
Running
rm -rf ./build && svelte-kit build
is a good enough workaround for now.The text was updated successfully, but these errors were encountered: