next.js
Don't blame the Pages Router for next/headers imported through a Client Component
#100087
Merged

Don't blame the Pages Router for next/headers imported through a Client Component #100087

lukesandberg
vercel-gh-bot-2[bot] test: add regression test for next/headers error blaming the Pages Ro…
67ba948b
lukesandberg fix: don't blame the Pages Router for next/headers imported via a Cli…
0c7d62da
lukesandberg Drop the app-router fixture convention and trim comments
75fa1d0b
github-actions github-actions added created-by: Turbopack team
github-actions github-actions added tests
github-actions github-actions added Turbopack
github-actions github-actions added type: next
github-actions
lukesandberg lukesandberg marked this pull request as ready for review 25 days ago
lukesandberg
lukesandberg commented on 2026-10-13
lukesandberg
lukesandberg commented on 2026-10-13
lukesandberg lukesandberg requested a review 25 days ago
lukesandberg Simplify is_app_router doc and use named fields for NextRscErrClientI…
cf12c289
mischnic
mischnic approved these changes on 2026-10-13
lukesandberg lukesandberg enabled auto-merge (squash) 25 days ago
lukesandberg lukesandberg merged ab5db580 into canary 25 days ago
lukesandberg lukesandberg deleted the next-maintainer/db5fd821b0b5a014/test-5c6f68354d3a97830980e56e branch 25 days ago
github-actions github-actions added locked
github-actions github-actions locked as resolved and limited conversation to collaborators 10 days ago

Login to write a write a comment.

Login via GitHub

Reviewers
Assignees
No one assigned
Labels
Milestone