nextjs - 💡(How to fix) Fix Newly created project gives: `Module not found: Can't resolve 'next-intl/middleware'` [5 comments, 5 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#87821Fetched 2026-04-08 02:06:04
View on GitHub
Comments
5
Participants
5
Timeline
13
Reactions
0
Timeline (top)
commented ×5mentioned ×2subscribed ×2closed ×1

Code Example

Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 23.5.0: Wed May  1 20:12:58 PDT 2024; root:xnu-10063.121.3~5/RELEASE_ARM64_T6000
  Available memory (MB): 65536
  Available CPU cores: 10
Binaries:
  Node: 22.14.0
  npm: 10.9.2
  Yarn: 1.22.22
  pnpm: 10.26.2
Relevant Packages:
  next: 16.1.1 // Latest available version is detected (16.1.1).
  eslint-config-next: N/A
  react: 19.2.3
  react-dom: 19.2.3
  typescript: 5.9.3
Next.js Config:
  output: N/A
RAW_BUFFERClick to expand / collapse

Link to the code that reproduces this issue

https://github.com/francosang/my-app

To Reproduce

pnpm create next-app@latest my-app --yes cd my-app pnpm dev

Current vs. Expected behavior

Current

App starts with errors.

<img width="1063" height="583" alt="Image" src="https://github.com/user-attachments/assets/d81621c8-e93d-427c-9138-7737fbcf9478" />

https://github.com/user-attachments/assets/3968a742-e764-42fa-a750-30148a4e04b3

Expected

App starts without errors

Provide environment information

Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 23.5.0: Wed May  1 20:12:58 PDT 2024; root:xnu-10063.121.3~5/RELEASE_ARM64_T6000
  Available memory (MB): 65536
  Available CPU cores: 10
Binaries:
  Node: 22.14.0
  npm: 10.9.2
  Yarn: 1.22.22
  pnpm: 10.26.2
Relevant Packages:
  next: 16.1.1 // Latest available version is detected (16.1.1).
  eslint-config-next: N/A
  react: 19.2.3
  react-dom: 19.2.3
  typescript: 5.9.3
Next.js Config:
  output: N/A

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

  • The most likely fix is to check the compatibility of the next version with the project's dependencies and try creating the app with a previous version of next to isolate the issue.

Guidance

  • Try creating the app with a previous version of next using pnpm create next-app@previous-version my-app --yes to see if the issue persists.
  • Verify the compatibility of the next version with the project's dependencies, such as react and react-dom, to ensure they are compatible with next version 16.1.1.
  • Check the official next documentation and GitHub issues for any known issues or breaking changes in version 16.1.1.
  • If the issue is not resolved, try updating the react and react-dom versions to the latest compatible versions with next version 16.1.1.

Notes

  • The issue may be related to a compatibility issue between next version 16.1.1 and the project's dependencies.
  • Without more information about the error messages, it's difficult to provide a more specific solution.

Recommendation

  • Apply workaround: Try creating the app with a previous version of next to isolate the issue, as the current version may have compatibility issues with the project's dependencies.

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 Newly created project gives: `Module not found: Can't resolve 'next-intl/middleware'` [5 comments, 5 participants]