Skip to main content
GoodFirstPicks
DashboardIssuesReposLeaderboard

GoodFirstPicks by Leaveitblank © 2026

CreatorRequest a RepoPrivacy PolicyTerms of Service
@next/swc-darwin-arm64 is duplicated in every instance of Next.JS and the size in disk is huge | GoodFirstPicks

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

vercel/next.js 4 comments 22d ago
View on GitHub
highopenScope: somewhat clearSkill match: maybeNext.jsTypeScriptReact

Why this is a good first issue

The issue involves optimizing binary storage across multiple Next.js instances, which requires architectural changes.

AI Summary

The issue highlights that the @next/swc-darwin-arm64 binary is duplicated in every Next.js instance, leading to significant disk usage. The proposed solution involves moving the binary to a shared location, which would require changes to how Next.js handles binary dependencies. This is a complex architectural change that may impact multiple areas of the codebase.

Issue Description

Link to the code that reproduces this issue

https://github.com/RodrigoTomeES/bug-nextjs-api-polyfill

To Reproduce

Ignore the link, just install the nextjs package

bunx 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 Labels

SWC

Want to work on this?

Claim this issue to let others know you're working on it. You'll earn 35 points when you complete it!

Risk Flags

  • cross-cutting changes
  • requires deep architectural knowledge
Loading labels...

Details

Points35 pts
Difficultyhigh
Scopesomewhat clear
Skill Matchmaybe
Test Focusedno