Skip to content

test(compat): restore fresh-render timestamp coverage - #3392

Open
camc314 wants to merge 3 commits into
cloudflare:mainfrom
camc314:codex/restore-fresh-render-timestamps
Open

camc314 wants to merge 3 commits into
cloudflare:mainfrom
camc314:codex/restore-fresh-render-timestamps

Conversation

@camc314

@camc314 camc314 commented Sep 22, 2026

Copy link
Copy Markdown
Contributor
  • Re-enable the app-rendering compatibility test that checks for fresh layout and page timestamps across development requests. The timestamp presence and inequality assertions stay intact; the stale module-cache diagnosis is removed and compatibility tracking counts are updated.
  • The test follows the Next.js app-rendering assertion. This covers development rendering; production ISR cache behavior and original upstream E2E verification remain separate.

The local port of Next.js app-rendering's ISR timestamp assertion was
still skipped with an old claim that use(getData()) cached timestamps
across requests. Running the unchanged assertion against the current
development server shows that both page and layout timestamps change.
No runtime fix or weakened assertion is needed.

Enable the test and remove the stale diagnosis and proposed module-cache
invalidation workaround. Keep the checks for timestamp presence as well
as inequality so missing HTML cannot make the test pass. Update the
tracking counts and explicitly limit this evidence to development
rendering, which does not establish production ISR cache behavior.
The mixed static/dynamic case remains skipped because upstream skips it.

Validation: the targeted app-rendering, head, shim, and document run passed
1394 tests with one upstream skip. vp check passed for the changed test;
formatting was applied to the tracking document. Original upstream E2E
verification remains separate from this local coverage restoration.

Upstream: https://github.com/vercel/next.js/blob/v16.2.6/test/e2e/app-dir/app-rendering/rendering.test.ts
Copilot AI lite review requested due to automatic review settings September 22, 2026 17:42

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

@pkg-pr-new

pkg-pr-new Bot commented Sep 22, 2026

Copy link
Copy Markdown

Open in StackBlitz

@vinext/cloudflare

npm i https://pkg.pr.new/@vinext/cloudflare@3392

create-vinext-app

npm i https://pkg.pr.new/create-vinext-app@3392

@vinext/types

npm i https://pkg.pr.new/@vinext/types@3392

vinext

npm i https://pkg.pr.new/vinext@3392

@cloudflare/workers-response-store

npm i https://pkg.pr.new/@cloudflare/workers-response-store@3392

commit: 2a0308f

@github-actions

github-actions Bot commented Sep 22, 2026

Copy link
Copy Markdown
Contributor

Performance benchmarks

Compared 2a0308f against base 087f8d6 using alternating same-runner rounds. Next.js was unchanged and skipped.

0 improved · 0 regressed · 6 within ±1.5%

Scenario Framework Baseline Current Change
Client bundle size (gzip) vinext 142.3 KB 142.3 KB ⚫ +0.0%
Client entry size (gzip) vinext 129.7 KB 129.7 KB ⚫ +0.0%
Dev server cold start vinext 3.53 s 3.53 s ⚫ -0.2%
Production build time vinext 4.04 s 4.07 s ⚫ +0.7%
RSC entry closure size (gzip) vinext 127.9 KB 127.9 KB ⚫ +0.0%
Server bundle size (gzip) vinext 226.0 KB 226.1 KB ⚫ +0.0%

View detailed results and traces

🟢 improvement · 🔴 regression · ⚫ change below 1.5% · paired base/head

@james-elicx

Copy link
Copy Markdown
Member

/bigbonk review for issues

Time limit: 8 minutes. Complete the review and post all findings within that limit.

Comment thread tests/nextjs-compat/TRACKING.md
Comment thread tests/nextjs-compat/TRACKING.md
@ask-bonk

ask-bonk Bot commented Sep 22, 2026

Copy link
Copy Markdown
Contributor

Posted 2 actionable inline findings.

github run

@james-elicx

Copy link
Copy Markdown
Member

/bigbonk review for issues

Time limit: 8 minutes. Complete the review and post all findings within that limit.

@ask-bonk

ask-bonk Bot commented Sep 22, 2026

Copy link
Copy Markdown
Contributor

LGTM!

github run

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants