mirror of
https://github.com/cloudflare/vinext.git
synced 2026-05-09 08:25:34 +02:00
[PR #949] [MERGED] fix: add experimental.prefetchInlining to compatibility check #977
Labels
No labels
enhancement
enhancement
good first issue
help wanted
nextjs-tracking
nextjs-tracking
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/vinext#977
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
📋 Pull Request Information
Original PR: https://github.com/cloudflare/vinext/pull/949
Author: @Divkix
Created: 4/29/2026
Status: ✅ Merged
Merged: 4/29/2026
Merged by: @james-elicx
Base:
main← Head:fix/860-prefetch-inlining📝 Commits (2)
c5c27fefix: add experimental.prefetchInlining to compatibility check (#860)133e8e3fix: mark experimental.prefetchInlining as partial, add test📊 Changes
2 files changed (+25 additions, -0 deletions)
View changed files
📝
packages/vinext/src/check.ts(+11 -0)📝
tests/check.test.ts(+14 -0)📄 Description
Fixes #860
Summary
experimental.prefetchInliningto theCONFIG_SUPPORTmap incheck.tsassupportedanalyzeConfig()forprefetchInliningin experimental config blocksprefetchInliningfromfalsetotrueby default — vinext uses unified RSC navigation payloads, so per-segment prefetch inlining is not applicableTest plan
pnpm run check(format, lint, types) — passespnpm test— 136 test files pass (4387 tests, 2 skipped)🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.