feat(integration): Add Next.js cache components test app #7728
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add integration test app for Next.js 16 cache components feature to validate Clerk's auth() behavior with the new cacheComponents config. Test scenarios: - auth() in server components, server actions, and API routes - 'use cache' correct pattern (auth outside, userId passed in) - 'use cache' error documentation - PPR with auth() - Protected routes via proxy Key findings: - ClerkProvider must be wrapped in Suspense for cache components - auth() inside 'use cache' functions produces build-time error - Route segment configs (dynamic) incompatible with cacheComponents
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
nikosdouvlis
approved these changes
Feb 2, 2026
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Adds integration test app for Next.js 16 cache components feature to validate Clerk's
auth()behavior with the newcacheComponentsconfig.Test Scenarios
auth()in server components, server actions, and API routes"use cache"correct pattern (auth outside, userId passed in)"use cache"error documentationauth()Key Findings
<Suspense>for cache components to workauth()inside"use cache"functions produces build-time errordynamic) incompatible withcacheComponentsexperimental.pprto top-levelcacheComponentsFiles Added
integration/templates/next-cache-components/- Full test appintegration/tests/cache-components.test.ts- E2E testsintegration/presets/next.tswithcacheComponentspresetTest plan
pnpm test:integration:next-cache-componentscd integration/templates/next-cache-components && pnpm build