Skip to content
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

[now dev] Use a different workPath for every build #2100

Merged
merged 1 commit into from
Apr 5, 2019

Conversation

TooTallNate
Copy link
Member

This is more inline with how a fresh Now deployment works, where is has to download fresh files each time. This will also fix the issue with @now/next that deleted the .next output dir and deleting static files upon subsequent builds.

This is still a bit unoptimized because prepareCache() from the builder is not yet being invoked, but it's still more correct than reusing the workPath.

This is more inline with how a fresh Now deployment works, where
is has to download fresh files each time. This will also fix the issue
with `@now/next` that deleted the `.next` output dir and deleting static
files upon subsequent builds.

This is still a bit unoptimized because `prepareCache()` from the
builder is not yet being invoked, but it's still more correct than
reusing the `workPath`.
@leo leo merged commit bd1aa22 into canary Apr 5, 2019
@leo leo deleted the update/now-dev-tmpdir-workPath branch April 5, 2019 00:22
leo pushed a commit that referenced this pull request Apr 5, 2019
This is more inline with how a fresh Now deployment works, where
is has to download fresh files each time. This will also fix the issue
with `@now/next` that deleted the `.next` output dir and deleting static
files upon subsequent builds.

This is still a bit unoptimized because `prepareCache()` from the
builder is not yet being invoked, but it's still more correct than
reusing the `workPath`.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants