Issue Station
Sign In
Tools hereToolbox

nextjs - ✅(Solved) Fix Does not work static rendering and ISR after update Next to 15.5+ ver [1 pull requests, 6 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#84944•Fetched 2026-04-08 02:17:55
View on GitHub
Comments
6
Participants
5
Timeline
12
Reactions
5
Author
lev3fonlev3fon
Participants
AriesMalaca-munrofgAriesMalaca-munrofglev3fonlev3fonN2D4N2D4olegkshlkvolegkshlkvwyattjohwyattjoh
Timeline (top)
commented ×6subscribed ×3mentioned ×2issue_type_added ×1

PR fix notes

PR #1072: Improve markdown availability for agent friendliness

Description (problem / solution / changelog)

Worked on the docs agent friendliness. The fix ensures agents can request for the md format of the docs content

<!-- This is an auto-generated comment: release notes by coderabbit.ai -->

Summary by CodeRabbit

  • New Features

    • Dedicated endpoints now serve documentation as plain-text and as markdown.
    • URLs for doc sections are mapped to their markdown sources for direct retrieval.

  • Improvements

    • Content format is automatically selected based on client preferences (Accept header / URL).
    • Copy-to-clipboard fetches the latest markdown directly from the server.
    • Pages emit a markdown alternate link for easier content negotiation.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->

Changed files

  • next.config.mjs (modified, +11/-0)
  • src/app/[[...slug]]/page.tsx (modified, +4/-1)
  • src/app/llms-full.txt/route.ts (added, +13/-0)
  • src/app/llms.mdx/[[...slug]]/route.ts (added, +22/-0)
  • src/app/llms.txt/route.ts (modified, +43/-44)
  • src/components/page-actions.tsx (modified, +6/-6)
  • src/lib/get-llm-text.ts (added, +41/-0)
  • src/middleware.ts (modified, +30/-4)

Code Example

Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 24.6.0: Mon Jul 14 11:30:40 PDT 2025; root:xnu-11417.140.69~1/RELEASE_ARM64_T6041
  Available memory (MB): 24576
  Available CPU cores: 14
Binaries:
  Node: 22.18.0
  npm: 10.9.3
  Yarn: 1.22.22
  pnpm: N/A
Relevant Packages:
  next: 15.5.5
  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/platforms

To Reproduce

  1. Update next to 15.5+
  2. add in ./app/s/[subdomain]/page.tsx ` export const dynamic = 'force-static';

export const revalidate = 1_000; ` 3) npm install 4) npm run build 5) npm run start 6) add subdomain, and go to new page (example: kek.localhost:3000) 7) reload page, check response headers - page not form cache

Current vs. Expected behavior

page always dynamic on 15.5+ ver, but on 15.3.2 works OK

Provide environment information

Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 24.6.0: Mon Jul 14 11:30:40 PDT 2025; root:xnu-11417.140.69~1/RELEASE_ARM64_T6041
  Available memory (MB): 24576
  Available CPU cores: 14
Binaries:
  Node: 22.18.0
  npm: 10.9.3
  Yarn: 1.22.22
  pnpm: N/A
Relevant Packages:
  next: 15.5.5
  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)

cacheComponents

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

next start (local)

Additional context

ISSUE duplicate from vercel/platforms: https://github.com/vercel/platforms/issues/478 (with proof videos)

extent analysis

TL;DR

Downgrade Next.js to version 15.3.2 to potentially resolve the caching issue with dynamic pages.

Guidance

  • Verify that the dynamic and revalidate properties in page.tsx are correctly set and not being overridden elsewhere in the code.
  • Check the response headers to confirm that the page is not being served from cache when using Next.js version 15.5+.
  • Review the Vercel platforms issue #478 for additional context and potential workarounds.
  • Consider testing with a minimal reproducible example to isolate the caching issue.

Example

No code snippet is provided as the issue is related to a specific version of Next.js and its interaction with caching.

Notes

The issue seems to be specific to Next.js version 15.5+ and may be related to changes in caching behavior. Downgrading to version 15.3.2 may resolve the issue, but it's essential to verify the fix and test thoroughly.

Recommendation

Apply workaround: Downgrade Next.js to version 15.3.2, as it is reported to work correctly in the issue description. This workaround may resolve the caching issue, but it's crucial to monitor the application's behavior and wait for an official fix or update from the Next.js team.

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…
#permission error#memory optimization#batch processing#GPU compatibility#latency issue

Still need to ship something?

×6

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

Back to top recommendations

TRENDING