-
Notifications
You must be signed in to change notification settings - Fork 129
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
clean before building #1568
clean before building #1568
Conversation
Code changes LGTM. If "clean" seems too inaccurate, maybe something like "clean-dist" (and then later "clean-cache", "clean-all"?) could be used. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Thinking about this some more, and I think cleaning the output directory is the right default, and probably doesn’t even need a flag. For precedence, Vite’s build command has an |
Sorry for posting to an old issue, but it seems like the best spot:
I've come here looking for a flag 😅 The problem is this: I'm using framework in a concourse pipeline, and the output directory is declared as the task's output, so that only that data is moved to the next task. Concourse seems to do that by mounting something into the output location, and that something cannot be removed:
I think I can just use another directory within the output directory, so it's probably not a big deal. |
Fixes #1538. Now
observable build
is always clean.Leaving as draft because I think we want a
--clean
flag to clean automatically, and without it we prompt you before cleaning the existing output root (if it exists) (and error in CI if the output root is dirty and--clean
or--no-clean
wasn’t specified).And maybe
--clean
isn’t the right name because a “clean” build will still respect the cache so it’s not fully clean? Sigh.