Issue Station
Sign In
Tools hereToolbox

nextjs - ✅(Solved) Fix Docs: Some links point to incorrect paths [1 pull requests, 2 comments, 3 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#86436•Fetched 2026-04-08 02:11:01
View on GitHub
Comments
2
Participants
3
Timeline
8
Reactions
0
Author
2u841r2u841r
Participants
2u841r2u841rgithub-actions[bot]github-actions[bot]icyJosephicyJoseph
Assignees
icyJosephicyJoseph
Timeline (top)
commented ×2assigned ×1closed ×1cross-referenced ×1

Fix Action

Fixed

PR fix notes

PR #86443: Fix incorrect GitHub link in ESLint config documentation

Description (problem / solution / changelog)

What?

This PR corrects an outdated GitHub link in the ESLint configuration documentation. The existing link pointed to the canary branch instead of the versioned next-15.5 tag.

Why?

The documentation page reflects Next.js 15.5, so the linked source file should match the same version. Leaving the link pointed at canary can lead to confusion, mismatched code, or 404s if paths change.

How?

Updated the incorrect link in docs/01-app/03-api-reference/05-config/03-eslint.mdx

Replaced:

/blob/canary/packages/eslint-config-next/index.js

with:

/blob/next-15.5/packages/eslint-config-next/index.js

Closes #86436

Additional Notes for Maintainers

This is a documentation improvement (no code changes).

Formatting preserved; file validated locally.

No tests required since this is a docs-only fix.

Changed files

  • docs/01-app/03-api-reference/04-functions/generate-sitemaps.mdx (modified, +14/-10)
  • docs/01-app/03-api-reference/05-config/03-eslint.mdx (modified, +1/-1)
RAW_BUFFERClick to expand / collapse

What is the documentation issue?

In this page- https://nextjs.org/docs/15/app/api-reference/config/eslint following links are broken

https://github.com/vercel/next.js/blob/55ef0e3ebc1d43e1a4a191341dc2a415e12124d4/docs/01-app/03-api-reference/05-config/03-eslint.mdx?plain=1#L279 https://github.com/vercel/next.js/blob/55ef0e3ebc1d43e1a4a191341dc2a415e12124d4/docs/01-app/03-api-reference/05-config/03-eslint.mdx?plain=1#L25-L47

Is there any context that might help us understand?

those links are sending to /canary https://github.com/vercel/next.js/blob/canary/packages/eslint-config-next/index.js

instead of current version (15.5 in our case) https://github.com/vercel/next.js/blob/next-15-5/packages/eslint-config-next/index.js

Does the docs page already exist? Please link to it.

https://nextjs.org/docs/15/app/api-reference/config/eslint

extent analysis

TL;DR

Update the broken links to point to the correct version, in this case, next-15-5, instead of canary.

Guidance

  • Verify the correct version of the documentation by checking the Next.js version being used (e.g., 15.5).
  • Update the links to point to the correct version, replacing canary with next-15-5 in the URL.
  • Check the documentation page for any other broken links that may need to be updated.
  • Consider reporting the issue to the Next.js documentation team to ensure the links are updated for all users.

Notes

The fix assumes that the correct version of the documentation is available on the GitHub repository. If the version is not available, the links may still be broken.

Recommendation

Apply workaround: Update the links to point to the correct version, as this will allow users to access the correct documentation until the official documentation is updated.

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…
#api#tool integration#LLM response#prompt template#agent execution

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 - ✅(Solved) Fix Docs: Some links point to incorrect paths [1 pull requests, 2 comments, 3 participants]