fix(config): make stacktrace path correct when sourcemap is enabled

[sapphi-red]

Description

fixes #18832

[pkg-pr-new]

Open in Stackblitz

npm i https://pkg.pr.new/vite@18833

commit: 7000908

[hi-ogawa]

I just veririfed the reproduction is fixed with pkg.pr.new, but for local playground, there's something odd regardless of NODE_OPTIONS. I added console.trace("test") and this is the log.

$ pnpm -C playground/html dev

> @vitejs/[email protected] dev /home/hiroshi/code/others/vite/playground/html
> vite

Trace: test
    at file:///home/hiroshi/code/others/vite/playground/html/node_modules/.vite-temp/file:/home/hiroshi/code/others/vite/playground/html/vite.config.js:4:9
    ...

[hi-ogawa]

Oh, it looks like source-map-support is breaking the stack when using cli locally

vite/packages/vite/bin/vite.js

Lines 5 to 10 in b39e696

	if (!import.meta.url.includes('node_modules')) {
	try {
	// only available as dev dependency
	await import('source-map-support').then((r) => r.default.install())
	} catch {}
	}

Can this be maybe changed to process.setSourceMapsEnabled(true)?

[sapphi-red]

I removed the pathToFileURL part as it seems it works without it. This should fix users that are enabling source-map-support before config load.

[sapphi-red]

Can this be maybe changed to process.setSourceMapsEnabled(true)?

Ah, yeah, maybe we can migrate to it in a separate PR.

[hi-ogawa]

Nice, thanks!

[bluwy]

Suggested change

	sourceRoot: path.dirname(fileName) + '/',
	sourceRoot: path.dirname(fileName) + path.sep,

Should this use path.sep since it could be backward slash now?