Debug Nexjs app in monorepo with "NODE_OPTIONS='inspect'" about nextjs-monorepo-example HOT 10 CLOSED

Yes, I use turbo in my app but in the playground i use plain nextjs app with npm. I want to start as simple as possible and understand what's happening

from nextjs-monorepo-example.

Let me know when you find out... super interested as well. And thanks for your work

from nextjs-monorepo-example.

Ok I think I found the right issue I'm having
I'm able to stop the debugger 🎉

The fix is in this PR which is still pending
vercel/next.js#51467

I wanted to try so I forked NextJS repo and copied these changes and looks it working

from nextjs-monorepo-example.

Thanks for the tip.

from nextjs-monorepo-example.

I'll have a look next week. It's totally new for me but nice you've shared it. Don't get too frustrated though, perfectly normal sometimes 😀

from nextjs-monorepo-example.

BTW really feel free to make a small pr with the dev:debug script on this repo. I'll merge and try.

from nextjs-monorepo-example.

Thanks! I'm trying to take a scientific aproach here 🤓 starting by standalone nextjs with javascript and go up to full monorepo pnpm typescript

https://github.com/andresgutgon/nextjs-debugging

So far I'm in the most simple case following their docs and I'm not understanding how debugging works in node. I did manage to debug a simple express one file server tho. So much be something related with nextjs and sourcemaps.

from nextjs-monorepo-example.

Nice. Have you tried it with a getserversideprops route ?

from nextjs-monorepo-example.

With default pages/api/hello which is ultra simple. The problem is that Chrome Dev Tools don't even see that code so I can't put a debugger

from nextjs-monorepo-example.

mmm. I saw that you use turbo to run the command, might be that too ? (ie https://github.com/vercel/turbo/blob/main/packages/turbo/install.js#L190)

from nextjs-monorepo-example.