vercel / vercel/platforms

Does not work static rendering and ISR after update Next to 15.5+ ver

Open
#478 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
6.7k
Forks
1.1k
PR merge metrics
No merged PRs in 30d

Description

After update Next ver to 15.5.5 every multi-tenet pages always rendering on server as dynamic = ''force-dynamic".

proofs:

Next 15.5.5 (no-cache page):

https://github.com/user-attachments/assets/19b0787c-a21f-4d31-bf23-55a506e4dd4f

Next 15.3.2 (page from cache):

https://github.com/user-attachments/assets/1faf64f0-39f8-47b5-89cc-18c9f008f430

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names no files, tests, or entry points. Reproduce the multi-tenant rendering behavior with Next.js 15.5.5 and compare it with 15.3.2, focusing on static rendering and ISR; done means affected pages can use caching or ISR instead of always rendering dynamically.

Written by the indexing model from the issue text.

Assessment

Tech stack
nextjs
Domain
web-dev
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.