console-dev/console-file.js showing up instead of real file on vs code debug

[mikelpr]

Summary

I don't know at what point in time this started happening but whenever I am debugging server-side all my console.log calls and thrown Errors trace to console-dev.js (next 15) or console-file.js (next 16)
I'm going insane over this. Searching I only find stuff about client side and sourceMaps and pathMappings for webpack and turbopack but my problem is server side

Additional information

launch configuration:

{
      "name": "Next.js: debug server-side",
      "type": "node-terminal",
      "request": "launch",
      "command": "npm run dev -- --inspect"
},

dev on package.json: next dev --turbopack

Example

No response

[icyJoseph]

Maybe? https://code.visualstudio.com/docs/nodejs/nodejs-debugging#_skipping-uninteresting-code if that works, we should document it 💀

[mikelpr]

it should totally be documented. https://nextjs.org/docs/app/guides/debugging#debugging-with-vs-code needs updating

EDIT: this is wrong. this is a yarn classic thing. keeping it here tho.
passing --inspect as an argument to node v22.21.1 (I don't know since which version) exits saying it's deprecated and that you should use NODE_OPTIONS=--inspect

[mikelpr]

thanks for this I was having a meltdown today.

[mikelpr]

should I file a bug about the documentation?

[icyJoseph]

Aha, wait, no the thing is that next dev supports --inspect in canary.

• Allow inspecting dev server on default port with next dev --inspect #85037

The doc update to the guide was likely made thinking to land this before, but it has been delayed. Apologies for that. next dev --inspect will work on the next minor most likely.

[mikelpr]

oh yeah, I was pretty confused right now as I opened another project that uses npm where it did fail, lol