debbugger unbound?

Is anyone having some issues with the vs code not bounding breakpoints? in the create-t3-turbo example tried a few things from here but still seeing some issues like it will only bind like to packages outside nextjs(e.g ./packages/api/**) but will also only bind ./app/nextjs/src/env.ts but nothing after that Has anyone experience anything similar? Look at this github issue and nothing seems to work either: https://github.com/vercel/next.js/issues/62008
GitHub
Debugger not binding breakpoints in VSCode in server components, us...
Link to the code that reproduces this issue https://github.com/andrewmartin/nextjs-example To Reproduce Open the code in VSCode Add a breakpoint in any server side files Open the "Run and Debu...
No description
No description
0 Replies
No replies yetBe the first to reply to this messageJoin
Want results from more Discord servers?
Add your server