Duplicate Imports from next/cache and build size increase

[m-elagamy]

https://github.com/m-elagamy/nextjs-cache-duplication

To Reproduce

1. Clone: git clone https://github.com/m-elagamy/nextjs-cache-duplication.git
2. Install: npm install
3. Build: npm run build
4. Observe:
   • Duplicate imports from 'next/cache' (e.g., revalidatePath, revalidateTag) in IDE autocomplete or build output.
   • Size increase (see below).

Current vs. Expected behavior

Actual Behavior

• All exports from 'next/cache' (e.g., revalidatePath, revalidateTag) are duplicated.
• Fresh size: 351MB
• Post-build size: 398MB

Expected Behavior

• Single import for each export from 'next/cache'.
• Build output should maintain reasonable size proportional to project complexity (without unexpected duplication of core modules).

Before building

After

Provide environment information

Operating System:
  Platform: win32
  Arch: x64
  Version: Windows 10 Pro
  Available memory (MB): 16295
  Available CPU cores: 4
Binaries:
  Node: 20.14.0
  npm: 10.7.0
  Yarn: N/A
  pnpm: 10.7.0
Relevant Packages:
  next: 15.2.4 // Latest available version is detected (15.2.4).
  eslint-config-next: N/A
  react: 19.1.0
  react-dom: 19.1.0
  typescript: N/A
Next.js Config:
  output: N/A

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

Performance

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

next build (local)

Additional Context

• Persists after cleaning node_modules and .next, reinstalling, and deduplicating.
• Repo: https://github.com/m-elagamy/nextjs-cache-duplication.git
• No custom next.config.js or extra dependencies beyond the default template.