-
Notifications
You must be signed in to change notification settings - Fork 63
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
feat: Get rid of node_modules
symlink
#2194
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 1 Ignored Deployment
|
This pull request is automatically built and testable in CodeSandbox. To see build info of the built libraries, click here or the icon next to each commit SHA. Latest deployment of this branch, based on commit d316b75:
|
This reverts commit 4d5a310.
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.
Good Job! ✨ (I'd recommend adding any description to this PR, even a simpler one)
I left some comments and curiosities along the review haha
Do you think in the future we can move some of the CLI job to the cicd workflow? to be less cli dependent, or would be cumbersome somehow?
@@ -45,7 +32,7 @@ async function copyResource(from: string, to: string) { | |||
removeSync(to) | |||
} | |||
|
|||
await copySync(from, to) | |||
copySync(from, to) |
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.
Good catch!
Co-authored-by: Eduardo Formiga <[email protected]>
These changes prevent the user's
node_modules
directory to be sent to the build pipeline and remove the symbolic link.Next.js standalone build only needs that to create the production-ready
.next/standalone
output.