Btw, I didn't come up with this idea on my own. @darklang introduced me to it. They called it "trace-driven development" and went way further by storing the HTTP request to develop against: youtu.be/LcQyAfKLLT0...
Introduction: Trace Driven Development
An introduction to developing from traces in Dark (the 404 section of the sidebar and the traces on HTTP handlers).
www.youtube.com
August 20, 2025 at 11:02 AM
Btw, I didn't come up with this idea on my own. @darklang introduced me to it. They called it "trace-driven development" and went way further by storing the HTTP request to develop against: youtu.be/LcQyAfKLLT0...
Error overlays already exist in Next.js and they can even deep link into your code editor to open the right file.
But they don't generate code fixes for you or even help scaffolding code.
But they don't generate code fixes for you or even help scaffolding code.
August 20, 2025 at 11:02 AM
Error overlays already exist in Next.js and they can even deep link into your code editor to open the right file.
But they don't generate code fixes for you or even help scaffolding code.
But they don't generate code fixes for you or even help scaffolding code.
I always felt it was a missed opportunity for dev tools to offer code scaffolding opportunities on the error pages of the app. Go from telling you about the error to predicting your next step.
August 20, 2025 at 11:02 AM
I always felt it was a missed opportunity for dev tools to offer code scaffolding opportunities on the error pages of the app. Go from telling you about the error to predicting your next step.