nextjs - 💡(How to fix) Fix SWC helpers version conflict: [email protected] uses @swc/[email protected] but @swc/[email protected] requires >=0.5.17 [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
vercel/next.js#84728Fetched 2026-04-08 02:18:42
View on GitHub
Comments
1
Participants
2
Timeline
4
Reactions
0
Timeline (top)
closed ×1commented ×1labeled ×1locked ×1

Error Message

Error message: npm error Invalid: lock file's @swc/[email protected] does not satisfy @swc/[email protected] npm error Missing: @swc/[email protected] from lock file

Root Cause

This creates a mismatch between the helper version bundled by Next.js and the one required by upstream SWC packages.

Because both depend on @swc/helpers as a shared peer, npm tries to deduplicate them, causing installation failure or inconsistent lockfiles.

Code Example

npm error Invalid: lock file's @swc/helpers@0.5.15 does not satisfy @swc/helpers@0.5.17
npm error Missing: @swc/helpers@0.5.17 from lock file
RAW_BUFFERClick to expand / collapse

Describe the problem

When using [email protected] together with other SWC-based tools (for example @vitejs/[email protected]), npm ci fails due to a version conflict between @swc/helpers versions required by different packages.

Error message:

npm error Invalid: lock file's @swc/[email protected] does not satisfy @swc/[email protected]
npm error Missing: @swc/[email protected] from lock file

Root cause

This creates a mismatch between the helper version bundled by Next.js and the one required by upstream SWC packages.

Because both depend on @swc/helpers as a shared peer, npm tries to deduplicate them, causing installation failure or inconsistent lockfiles.

Why this matters

This affects:

  • Monorepos or projects using both Next.js and other SWC-based tools (e.g. Vite, Jest SWC plugins)
  • CI environments that use npm ci, where the lockfile must be exact
  • Dependency resolution reproducibility across platforms

Suggested fix

Update Next.js’s internal dependency on @swc/helpers from 0.5.150.5.17 (or newer), to stay consistent with the version required by the current @swc/[email protected] release.

Environment

  • Next.js: 15.5.4
  • @swc/core: 1.13.5
  • @vitejs/plugin-react-swc: 4.1.0
  • Node.js: 20.19.0
  • npm: 10.8.2
  • OS: macOS 14 (Apple Silicon)

extent analysis

TL;DR

Update Next.js's internal dependency on @swc/helpers to version 0.5.17 or newer to resolve the version conflict.

Guidance

  • Verify the versions of @swc/helpers required by different packages in your project to identify potential conflicts.
  • Consider updating next to a version that uses @swc/helpers version 0.5.17 or newer, if available.
  • If updating next is not feasible, explore using a different version of @vitejs/plugin-react-swc that is compatible with the @swc/helpers version used by next.
  • Check the project's lockfile for inconsistencies and consider regenerating it after updating dependencies.

Example

No code snippet is provided as the issue is related to dependency version conflicts rather than code implementation.

Notes

The suggested fix assumes that updating next to use a newer version of @swc/helpers is feasible and compatible with the project's requirements. Additionally, the issue may be resolved in future versions of next or @vitejs/plugin-react-swc, so it's essential to monitor updates and release notes.

Recommendation

Apply workaround: Update next to use @swc/helpers version 0.5.17 or newer, as this resolves the version conflict and ensures consistent dependency resolution.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

nextjs - 💡(How to fix) Fix SWC helpers version conflict: next@15.5.4 uses @swc/helpers@0.5.15 but @swc/core@1.13.5 requires >=0.5.17 [1 comments, 2 participants]