TS source for source maps in node_modules are processed by Vite pipeline when requested by the devtools

[DrUNE]

Hi, when i connect external library with provided source mapping and sources i cannot get correct source mapping for debugging, all i get is wrapped in hot reload transpiled content. Side bar sows correctly selected file in node_modules path in src directory, but real content is completely different. Is there any way i can enable mapping, so it works like in project with CRA?

[ArnaudBarre]

Hi, can you try to provide a minimal repro with your workspace/node_modules setup (one file app with one file "external" lib)? It would help get me started a lot quicker

[DrUNE]

Hi, can you try to provide a minimal repro with your workspace/node_modules setup (one file app with one file "external" lib)? It would help get me started a lot quicker

Sure, i have created minimal component library for testing this purpose @drune/naive-soursemapped-panel and two repo web apps, one of which is Create react app template $ npm create react-app@latest -- cra-web-app --template typescript, another is vite $ npm create vite@latest vite-swc-web-app --template react-swc-ts
In both installed library and added minimal use of the component.
All 3 repo:
https://github.com/DrUNE/cra-web-app
https://github.com/DrUNE/vite-swc-web-app
https://github.com/DrUNE/naive-soursemapped-panel

[DrUNE]

In CRA sources mapped correctly to file of library

[DrUNE]

In Vite-SWC project only sources that belongs to web app have correct mappings, but not the ones from library (path is correct, but source is totally different):

[ArnaudBarre]

Thanks for the repro, I will look at it this weekend!

[ArnaudBarre]

Ok so the issue is that the file is processed by the Vite pipeline instead of being ignored and returned as is.
This should be fixed in core.
I just asked the team if this is an issue they have already seen.
I'm trying to see if this is easy for us to differentiate requests for source code from request from the devtools

[bluwy]

Similar (but not sure if it's a duplicate): #11743

[sapphi-red]

I checked the repro. It seems there's a bug in esbuild: evanw/esbuild#3144

[sapphi-red]

If you have control of the library, you can remove sourcesContent field from the sourcemap of the library (or generate a sourcesContent field that doesn't include any nulls) for a workaround.
After changing that, you might need to run Vite with --force initially.

[ArnaudBarre]

How does this null in source content relate to this issue?

[sapphi-red]

When null is in the sourcesContent field, the browser fetches the content based on the value in sources field.