-
Notifications
You must be signed in to change notification settings - Fork 22
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
fix: copying excess files to output directory #101
Conversation
🦋 Changeset detectedLatest commit: 63daa64 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
commit: |
7b0d08d
to
8076b05
Compare
35209d0
to
4d1da8e
Compare
4d1da8e
to
63daa64
Compare
|
||
fix: copying excess files to output directory | ||
|
||
In previous versions, we copied the entire `.next` directory to the `.worker-next` output directory. Going forward, it will only copy the `.next/standalone` directory to this location. |
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.
In previous versions, we copied the entire `.next` directory to the `.worker-next` output directory. Going forward, it will only copy the `.next/standalone` directory to this location. | |
In previous versions, we copied the entire `.next` directory to the `.worker-next` output directory. Since this is not necessary, going forward, we will only copy the `.next/standalone` directory to this location. |
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.
We should move away from this copy when we integrate with open next.
Then I don't think there is a need to change that now.
Context
We currently copy everything in .next to the output directory when we only utilise .next/standalone.
Changes