Source maps aren't loaded correctly in Chrome Node DevTools

[pbadenski]

I ran node --inspect-brk -r @swc/register some_script.ts and then opened chrome://inspect - DevTools for Node. Source maps weren't loaded properly (was showing a transpiled JS content under a TS filename). I checked with babel and it works fine. There seems to be a difference between babel and swc that makes it break - I used debugger to dynamically modify swc source maps and managed to see it working.

It looks like embedding full filename path in sources doesn't work in Chrome DevTools for Node. What babel does, and seems to make it work - is encodes directory path in sourceRoot and just filename in sources.

This works (babel):

{
  "version": 3,
  "sourceRoot": "/Users/pbadenski/workspace/project/",
  "sources": [
    "test.ts"
  ],
  ...
}

This doesn't (swc):

{
  "version": 3,
  "sources": [
    "/Users/pbadenski/workspace/project/test.ts"
  ],
  ...
}

[kdy1]

Can you try https://swc.rs/docs/configuring-swc/#inlinesourcescontent ?

[pbadenski]

I tried, doesn't help unfortunately.

[egilsster]

Tried (a variation of options with inlineSourcesContent and sourceMaps) with 118 and 119 just now in VSCode and neither is working correctly at the moment while babel-loader is working. Running Jest in a debugging terminal in VSCode and none of my breakpoints are hitting. Simply reporting back but don't have the bandwidth to investigate that issue right now. Will create an issue if I manage to get a repro up.

NOTE: I am using a project with swc packages only (not the swc-node variant):

"@swc/core": "1.2.119",
"@swc/jest": "0.2.14",
"swc-loader": "0.1.15",

[kwonoj]

It looks like there are multiple different roots to investigate (from @swc/register to something else). Anyone experiencing this issue mind share exact repro steps for each? It's hard to do guesswork with currently known information.

[pbadenski]

Just FYI looks, I'm extremely happy. I haven't had any problems since recently - I will keep this thread updated. Thank you!! ⭐

[kdy1]

Can you try the latest version of @swc/core? (v1.2.155)

Patches in #4007 are very likely to fix this issue.

[kdy1]

Can anyone make an executable repro case?
node.js seems to consume sourcemap of swc without any problem.

See https://github.com/kdy1/swc/tree/6cea544afa481e063cff6d8d493d8d12dadb280a/crates/swc/tests/stacktrace for exmaple repro case.

[kdy1]

Can you try the latest version? (v1.2.156)
There was a bug fix for a module that only contains export * from './foo' and such module is super common, so I think it can be the cause of this.

[daviduzumeri]

If it helps, I'm still having the same issue and was able to create a quick repo to reproduce it: https://github.com/daviduzumeri/swctest

Any help would be appreciated, as we're pretty much back to console.log debugging over here.

[kdy1]

I found that sourcemap crate does not support sourceRoot.
https://docs.rs/sourcemap/6.1.0/sourcemap/struct.SourceMapBuilder.html

[kdy1]

Ref: getsentry/rust-sourcemap#50

[swc-bot]

This closed issue has been automatically locked because it had no new activity for a month. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.