nextjs - 💡(How to fix) Fix Wrong link in nextjs dev tools error dialogue when using "use cache" directive with no cacheComponents feature flag set [1 comments, 2 participants]

nextjs2025-10-27 10:29:00

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.

GitHub issue URL

Helpful · Quick feedback

GitHub stats

vercel/next.js#85397•Fetched 2026-04-08 02:15:58

View on GitHub

Comments

Participants

Timeline

Reactions

Author

serjdrn

Participants

github-actions[bot]

serjdrn

Timeline (top)

labeled ×2closed ×1commented ×1issue_type_added ×1

Error Message

Ecmascript file had an error Actual > https://nextjs.org/docs/canary/app/api-reference/directives/use-cache#usage throws 404 error Error Handling

Code Example

Ecmascript file had an error
> 1 | 'use cache'
    | ^^^^^^^^^^^

To use "use cache", please enable the feature flag `cacheComponents` in your Next.js config.

Read more: **https://nextjs.org/docs/canary/app/api-reference/directives/use-cache#usage**

---

Operating System:
  Platform: win32
  Arch: x64
  Version: Windows 11 Pro
  Available memory (MB): 32528
  Available CPU cores: 8
Binaries:
  Node: 22.16.0
  npm: 11.2.0
  Yarn: N/A
  pnpm: N/A
Relevant Packages:
  next: 16.0.0 // Latest available version is detected (16.0.0).
  eslint-config-next: N/A
  react: 19.2.0
  react-dom: 19.2.0
  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/vercel/next.js

To Reproduce

Start app in local dev
Use the "use cache" flag without having cacheComponents feature flag enabled
Click the link to proper usage

Current vs. Expected behavior

Ecmascript file had an error
> 1 | 'use cache'
    | ^^^^^^^^^^^

To use "use cache", please enable the feature flag `cacheComponents` in your Next.js config.

Read more: **https://nextjs.org/docs/canary/app/api-reference/directives/use-cache#usage**

Expected > https://nextjs.org/docs/app/api-reference/directives/use-cache

Actual > https://nextjs.org/docs/canary/app/api-reference/directives/use-cache#usage throws 404 error

This link needs updating https://nextjs.org/docs/canary/app/api-reference/directives/use-cache#usage to the one that works

Provide environment information

Operating System:
  Platform: win32
  Arch: x64
  Version: Windows 11 Pro
  Available memory (MB): 32528
  Available CPU cores: 8
Binaries:
  Node: 22.16.0
  npm: 11.2.0
  Yarn: N/A
  pnpm: N/A
Relevant Packages:
  next: 16.0.0 // Latest available version is detected (16.0.0).
  eslint-config-next: N/A
  react: 19.2.0
  react-dom: 19.2.0
  typescript: 5.9.3
Next.js Config:
  output: N/A

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

Error Handling

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

next dev (local)

Additional context

No response

extent analysis

TL;DR

Enable the cacheComponents feature flag in the Next.js config to resolve the error when using the "use cache" flag.

Guidance

The error message indicates that the cacheComponents feature flag is not enabled, which is required to use the "use cache" flag.
To fix the issue, update the Next.js config to include the cacheComponents feature flag.
Verify that the cacheComponents feature flag is correctly enabled by checking the Next.js config file.
Update the link in the error message to point to the correct documentation: https://nextjs.org/docs/app/api-reference/directives/use-cache.

Example

No code snippet is provided as it is not necessary for this issue.

Notes

The issue is specific to the next dev stage and is related to Error Handling. The fix should be applied to the local development environment.

Recommendation

Apply workaround: Enable the cacheComponents feature flag in the Next.js config, as this is the required step to resolve the error when using the "use cache" flag.

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?

#api #dependency error #configuration error #environment variable #network issue

Still need to ship something?

×6

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

Data

Security

Network

Code

UI/UX

Text

System

Multimedia

Protocol

API

Engineering

nextjs - 💡(How to fix) Fix Wrong link in nextjs dev tools error dialogue when using "use cache" directive with no cacheComponents feature flag set [1 comments, 2 participants]

Recommended Tools

GitHub issue graph ai analysis

Error Message

Code Example

Link to the code that reproduces this issue

To Reproduce

Current vs. Expected behavior

Provide environment information

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

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

Additional context

extent analysis

TL;DR

Guidance

Example

Notes

Recommendation

Still need to ship something?

TRENDING

nextjs - 💡(How to fix) Fix Wrong link in nextjs dev tools error dialogue when using "use cache" directive with no cacheComponents feature flag set [1 comments, 2 participants]

Recommended Tools

GitHub issue graph ai analysis

Error Message

Code Example

Link to the code that reproduces this issue

To Reproduce

Current vs. Expected behavior

Provide environment information

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

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

Additional context

extent analysis

TL;DR

Guidance

Example

Notes

Recommendation

Still need to ship something?

RELATED_DISCOVERY

TRENDING