nextjs - 💡(How to fix) Fix next js 15 is completely impossible to dev with [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#84047Fetched 2026-04-08 02:20:45
View on GitHub
Comments
1
Participants
2
Timeline
5
Reactions
0
Author
Timeline (top)
closed ×1commented ×1issue_type_added ×1labeled ×1

Code Example

You got us all into using next js, and now it is crushing and slow - impossible to work with. especially with a debugger.

Please get yourself together - fix it, or move back to what ever was working good on v14 - it is absolutely outrageous that a production level product degraded like this when thousand of company are depended on it
RAW_BUFFERClick to expand / collapse

Link to the code that reproduces this issue

https://github.com/vercel/next.js/issues

To Reproduce

You got us all into using next js, and now it is crushing and slow - impossible to work with. especially with a debugger.

Please get yourself together - fix it, or move back to what ever was working good on v14 - it is absolutely outrageous that a production level product degraded like this when thousand of company are depended on it

Current vs. Expected behavior

You got us all into using next js, and now it is crushing and slow - impossible to work with. especially with a debugger.

Please get yourself together - fix it, or move back to what ever was working good on v14 - it is absolutely outrageous that a production level product degraded like this when thousand of company are depended on it

Provide environment information

You got us all into using next js, and now it is crushing and slow - impossible to work with. especially with a debugger.

Please get yourself together - fix it, or move back to what ever was working good on v14 - it is absolutely outrageous that a production level product degraded like this when thousand of company are depended on it

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

Not sure

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

next dev (local)

Additional context

No response

extent analysis

TL;DR

Revert to Next.js version 14 as a temporary workaround to alleviate performance issues.

Guidance

  • Try downgrading Next.js to version 14 to see if the performance issues are resolved, as the user mentions it was working well on that version.
  • Investigate if there are any known issues or open tickets on the Next.js GitHub repository related to performance degradation in the current version.
  • Check if the issue persists when not using a debugger, to isolate if the problem is specific to debugging or a broader performance issue.
  • Consider providing more detailed environment information and steps to reproduce the issue to help the Next.js team diagnose and fix the problem.

Notes

The provided environment information is not useful for debugging, as it contains the same text as the problem description. More detailed information about the environment, such as the operating system, Node.js version, and any relevant configuration files, would be necessary to provide a more accurate diagnosis.

Recommendation

Apply workaround: Revert to Next.js version 14, as it is mentioned to have worked well in the past and may provide a temporary solution to the performance issues.

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 next js 15 is completely impossible to dev with [1 comments, 2 participants]