Cannot change SourceMaps path if esbuild is not used

[croban]

Describe the bug

For the dev mode, I am using Babel for transpiling typescript and not esbuild which is turned off inside vite.config.
In that case all sourcemaps (..."sources":["app.ts"]) have only relative paths and not absolute path as they have when esbuild is used. It seems that default rollup sourcemap settings are used because exactly the same output I am getting using only rollup.
There is not way to create sourceMaps with absolute path or maybe I miss something.
e.g.

sourcemapPathTransform: (relativeSourcePath, sourcemapPath) => {
            // will replace relative paths with absolute paths
            return path.resolve(
              path.dirname(sourcemapPath),
              relativeSourcePath
            );
},

Reproduction

https://stackblitz.com/edit/vitejs-vite-kn5643?file=vite.config.js

System Info

npx envinfo --system --npmPackages '{vite,@vitejs/*}' --binaries --browsers

Used Package Manager

npm

Logs

No response

Validations

• Follow our Code of Conduct
• Read the Contributing Guidelines.
• Read the docs.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to https://github.com/vuejs/core instead.
• Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
• The provided reproduction is a minimal reproducible example of the bug.

[sapphi-red]

What is the reason you want to change sourcemap paths during dev?

[croban]

What is the reason you want to change sourcemap paths during dev?

Because breakpoints and debugging within vscode don't work.

[sapphi-red]

Then, I think if #2950 is implemented, it is possible to solve with sourceMapPathOverrides.
https://github.com/microsoft/vscode-chrome-debug/blob/master/README.md#sourcemaps

[croban]

That would also solve my problem, just I don't have any patter which I could replace.
All SourceMap paths ends up with just filename.js without any paths (relative or absolute).
e.g.
src/components/fileone.js
src/lib/filetwo.js
src/file.js
ends with sources like ... ["sources":["filewhatever.js"]].

I could solved those paths problems on my side by using custom createBabelInputPluginFactory after that I had still problems with svelte which I solved with using experimental: dynamicCompileOptions. That experience was painful.

It would be great if default sourcemapPathTransform from rollup could be changed for vite dev.

[TFTomSun]

I stumbled over the same issue but with a different use case. I have some folders linked into the workspace using symbolic links. For some reasons, that breakpoint resolution within symlinked files is not working (Windows) so I tried out using sourceMapPathOverrides option to workaround it. It took me a couple of hours until I found out that the sources are just plain file names without any path information. This also prevents me from using sourceMapPathOverrides to point to the symlinked files so that the breakpoints get resolved.

With some hardcoded mapping (e.g. "myfile.ts": "<path-to-the-same-symlinked-filed") works

Is there any workaround to get path information into the source map file information?

[bluedusk]

is this solved ? I still can not debug Vite+React+TS. the breakpoints just dont hit

[mengdu]

Got the same problem while debugging ssrLoadModule in VSCode

[sapphi-red]

Closing as the VSCode debugger should work with JS files by #13514