8000 @next/swc-darwin-arm64 is duplicated in every instance of Next.JS and the size in disk is huge · Issue #79768 · vercel/next.js · GitHub
[go: up one dir, main page]
Skip to content

@next/swc-darwin-arm64 is duplicated in every instance of Next.JS and the size in disk is huge #79768

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.

Sign up for GitHub

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

Jump to bottom
Closed
RodrigoTomeES opened this issue May 28, 2025 · 1 comment
Closed

@next/swc-darwin-arm64 is duplicated in every instance of Next.JS and the size in disk is huge #79768

RodrigoTomeES opened this issue May 28, 2025 · 1 comment
Labels
invalid link The issue was auto-closed due to a missing/invalid reproduction link. A new issue should be opened. SWC Related to minification/transpilation in Next.js.

Comments

@RodrigoTomeES
Copy link
Contributor

Link to the code that reproduces this issue

Just install Next.JS in an ARM Mac

To Reproduce

npx create-next-app@latest

Current vs. Expected behavior

Right now the binary is in every instance of a Next.JS project it would be great if the binary is located in a shared route of the computer instead of having the "same" binary every time.

I don't know if this will be possible, but it will be a great improvement.

Image

Provide environment information

Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 24.5.0: Tue Apr 22 19:54:25 PDT 2025; root:xnu-11417.121.6~2/RELEASE_ARM64_T6020
  Available memory (MB): 32768
  Available CPU cores: 10
Binaries:
  Node: 22.11.0
  npm: 10.8.2
  Yarn: 1.22.22
  pnpm: 9.15.1
Relevant Packages:
  next: 15.2.4 // There is a newer version (15.3.2) available, upgrade recommended! 
  eslint-config-next: 15.1.7
  react: 18.3.1
  react-dom: 18.3.1
  typescript: 5.7.3
Next.js Config:
  output: standalone
 ⚠ There is a newer version (15.3.2) available, upgrade recommended! 
   Please try the latest canary version (`npm install next@canary`) to confirm the issue still exists before creating a new issue.
   Read more - https://nextjs.org/docs/messages/opening-an-issue

Which area(s) are affected? (Select all that apply)

SWC

Which stage(s) are affected? (Select all that apply)

Other (Deployed)

Additional context

No response
@github-actions github-actions bot added the SWC Related to minification/transpilation in Next.js. label May 28, 2025
@github-actions github-actions bot added the invalid link The issue was auto-closed due to a missing/invalid reproduction link. A new issue should be opened. label May 28, 2025
@github-actions GitHub Actions
Copy link
Contributor

We could not detect a valid reproduction link. Make sure to follow the bug report template carefully.

Why was this issue closed?

To be able to investigate, we need access to a reproduction to identify what triggered the issue. We need a link to a public GitHub repository (template for App Router, template for Pages Router), but you can also use these templates: CodeSandbox: App Router or CodeSandbox: Pages Router.

The bug template that you filled out has a section called "Link to the code that reproduces this issue", which is where you should provide the link to the reproduction.

  • If you did not provide a link or the link you provided is not valid, we will close the issue.
  • If you provide a link to a private repository, we will close the issue.
  • If you provide a link to a repository but not in the correct section, we will close the issue.

What should I do?

Depending on the reason the issue was closed, you can do the following:

  • If you did not provide a link, please open a new issue with a link to a reproduction.
  • If you provided a link to a private repository, please open a new issue with a link to a public repository.
  • If you provided a link to a repository but not in the correct section, please open a new issue with a link to a reproduction in the correct section.

In general, assume that we should not go through a lengthy onboarding process at your company code only to be able to verify an issue.

My repository is private and cannot make it public

In most cases, a private repo will not be a sufficient minimal reproduction, as this codebase might contain a lot of unrelated parts that would make our investigation take longer. Please do not make it public. Instead, create a new repository using the templates above, adding the relevant code to reproduce the issue. Common things to look out for:

  • Remove any code that is not related to the issue. (pages, API routes, components, etc.)
  • Remove any dependencies that are not related to the issue.
  • Remove any third-party service that would require us to sign up for an account to reproduce the issue.
  • Remove any environment variables that are not related to the issue.
  • Remove private packages that we do not have access to.
  • If the issue is not related to a monorepo specifically, try to reproduce the issue without a complex monorepo setup

I did not open this issue, but it is relevant to me, what can I do to help?

Anyone experiencing the same issue is welcome to provide a minimal reproduction following the above steps by opening a new issue.

I think my reproduction is good enough, why aren't you looking into it quickly?

We look into every Next.js issue and constantly monitor open issues for new comments.

However, sometimes we might miss one or two due to the popularity/high traffic of the repository. We apologize, and kindly ask you to refrain from tagging core maintainers, as that will usually not result in increased priority.

Upvoting issues to show your interest will help us prioritize and address them as quickly as possible. That said, every issue is important to us, and if an issue gets closed by accident, we encourage you to open a new one linking to the old issue and we will look into it.

Useful Resources
6399

@github-actions github-actions bot locked and limited conversation to collaborators May 28, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
invalid link The issue was auto-closed due to a missing/invalid reproduction link. A new issue should be opened. SWC Related to minification/transpilation in Next.js.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@RodrigoTomeES
0