Stacktraces are gone and dev experience suffers #74925

[haf]

Link to the code that reproduces this issue

https://github.com/haf/ffs-verecel

To Reproduce

Run the app to see the demo.

Try to figure out the input to ThrowingComponent and what component rendered it in a large project, where ThrowingComponent is rendered from multiple async components, layouts, pages, etc. You can't, because the stack trace is missing!

Current vs. Expected behavior

See example

Provide environment information

https://github.com/vercel/next.js/issues/74925

Which area(s) are affected? (Select all that apply)

Developer Experience

Which stage(s) are affected? (Select all that apply)

next dev (local), next start (local), Vercel (Deployed), Other (Deployed)

Additional context

#74925