Next 15 breakpoints and source map issues

[anthonyalayo]

Summary

Hey all,

Is anyone else encountering an issue with Next 15 where breakpoints don't align with the source? When I downgrade to Next 14, it doesn't occur. I would expect more complaints about this, but maybe everyone is just using print statements?

Additional information

No response

Example

No response

[icyJoseph]

In which Next 15 version? I recently debugged an issue on my site, with a debugger statement, didn't experience any issue.

[icyJoseph]

Yeah, sadly the project got attacked a couple of times by spammers, that created numerous issues by the minute. GitHub's security or, easy-ness to create accounts is not that good. So yeah, they had to make, creating an issue, a very specific kind of work.

[icyJoseph]

Well interesting, I often add the breakpoints on the Node Inspect tool , or manually drop a debugger statement, and that works. Are you able to verify this on other IDE's?

[anthonyalayo]

@icyJoseph I haven't tried other IDEs yet, but I think I spotted proof of it: #62008

These users are using VSCode, and I can see that they are setting workarounds to mitigate the bug:

Then i check vscode "Loaded Scripts" tab.
Notice that files i need to debug stored in - Next.js: debug full stack -> start-server.js -> my-app -> src -> app
so i put

"start-server.js/": "${workspaceFolder}/"

and it works for me.

[anthonyalayo]

I commented on this related issue that I think is covering the same problem. I also tried to write some sort of webpack config that can override the config from nextjs, but that had issues too.

[jukkaleh-atoz]

When using turbopack on dev breakpoints where broken on next 15.1.7

  "scripts": {
    "dev": "next dev --turbopack",
  },

After removing --turbopack they started working again