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

feat: Get rid of node_modules symlink #2194

Merged
merged 24 commits into from
Jan 16, 2024
Merged

feat: Get rid of node_modules symlink #2194

merged 24 commits into from
Jan 16, 2024

Conversation

gvc
Copy link
Contributor

@gvc gvc commented Jan 9, 2024

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.

Copy link

vercel bot commented Jan 9, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

1 Ignored Deployment
Name Status Preview Comments Updated (UTC)
faststore-site ⬜️ Ignored (Inspect) Visit Preview Jan 16, 2024 5:14pm

Copy link

codesandbox-ci bot commented Jan 9, 2024

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:

Sandbox Source
Store UI Typescript Configuration

@lucasfp13 lucasfp13 changed the title Get rid of symlink feat: Get rid of node_modules symlink Jan 11, 2024
@lucasfp13 lucasfp13 marked this pull request as ready for review January 11, 2024 14:18
@lucasfp13 lucasfp13 requested a review from a team as a code owner January 11, 2024 14:18
@lucasfp13 lucasfp13 requested review from eduardoformiga and lucasfp13 and removed request for a team January 11, 2024 14:18
Copy link
Member

@eduardoformiga eduardoformiga left a 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?

packages/cli/src/commands/build.ts Show resolved Hide resolved
packages/cli/src/commands/build.ts Show resolved Hide resolved
packages/cli/src/commands/build.ts Outdated Show resolved Hide resolved
packages/cli/src/commands/build.ts Show resolved Hide resolved
@@ -45,7 +32,7 @@ async function copyResource(from: string, to: string) {
removeSync(to)
}

await copySync(from, to)
copySync(from, to)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good catch!

packages/cli/src/commands/build.ts Show resolved Hide resolved
packages/cli/src/commands/build.ts Show resolved Hide resolved
packages/cli/src/commands/build.ts Show resolved Hide resolved
packages/core/next.config.js Outdated Show resolved Hide resolved
@lucasfp13 lucasfp13 merged commit 6d95a50 into main Jan 16, 2024
7 checks passed
@lucasfp13 lucasfp13 deleted the get-rid-of-symlink branch January 16, 2024 17:37
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.

3 participants