Closed
Description
Link to the code that reproduces this issue
https://github.com/vercel-labs/nextgram
To Reproduce
Run next dev --turbo
with app that uses route interception
Current vs. Expected behavior
It should work
Verify canary release
- I verified that the issue exists in the latest Next.js canary release
Provide environment information
n/a
Which area(s) are affected? (Select all that apply)
Turbopack (--turbo)
Additional context
No response