[GH-ISSUE #756] Static/dynamic detection #167

New issue

Closed

opened 2026-05-06 12:37:49 +02:00 by BreizhHardware · 0 comments

BreizhHardware commented

2026-05-06 12:37:49 +02:00

Owner

Originally created by @NathanDrake2406 on GitHub (Apr 2, 2026).
Original GitHub issue: https://github.com/cloudflare/vinext/issues/756

Problem

Pls refer to https://github.com/cloudflare/vinext/issues/726 for context

Phase 1 layout persistence works by always rendering all entries on the server and merging them on the client.

The planned Phase 3 skip-header optimization (X-Vinext-Router-Skip) needs to know which layout entries are safe to skip re-rendering. That requires a way to classify persisted layout entries as either:

static: safe to reuse from client cache
dynamic: must be re-rendered, or later handled with explicit stale-time semantics

Without this classification, skip-header work has no reliable foundation. This can be based off main I think since it's orthogonal

Originally created by @NathanDrake2406 on GitHub (Apr 2, 2026). Original GitHub issue: https://github.com/cloudflare/vinext/issues/756 ## Problem Pls refer to https://github.com/cloudflare/vinext/issues/726 for context Phase 1 layout persistence works by always rendering all entries on the server and merging them on the client. The planned Phase 3 skip-header optimization (`X-Vinext-Router-Skip`) needs to know which layout entries are safe to skip re-rendering. That requires a way to classify persisted layout entries as either: - static: safe to reuse from client cache - dynamic: must be re-rendered, or later handled with explicit stale-time semantics Without this classification, skip-header work has no reliable foundation. This can be based off main I think since it's orthogonal