Skip to content

Conversation

@H01001000
Copy link
Contributor

In the early development stage of the cache component (Dynamic I/O), PR #71285 makes Next.js not cache cache that either revalidate immediately (revalidate: 0), or expire in 5 min (expire < DYNAMIC_EXPIRE), besides it throws it as "without a Suspense boundary nor a "use cache" ". E.g., using the default cacheLife("seconds") profile, which has expire: 1 minute, Next.JS will mark is dynamic and throw above error.

Multiple issues have mentioned it: #74158, #74534, #78269.

For best going forward, unless better docs, reason, and bypass method in place, I think removing it makes cache component more predictable and gain more traction

@ijjk
Copy link
Member

ijjk commented Nov 20, 2025

Allow CI Workflow Run

  • approve CI run for commit: 2487347

Note: this should only be enabled once the PR is ready to go and can only be enabled by a maintainer

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants