Feature to preserve original file names and file paths in stack (after bunding)

[pjebs]

Description

During npm run dev, the stack trace contains information about the chain of calling functions (most importantly their file name and path).
After npm run build and then npm run preview, the stack trace loses all of that original information (since after bundling it is the one file).

I was wondering if vite can make it possible for me to find that information (without a source map) for some key functions that I can mark to Vite.

Suggested solution

Not sure

Alternative

No response

Additional context

No response

Validations

• Follow our Code of Conduct
• Read the Contributing Guidelines.
• Read the docs.
• Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

[pjebs]

See: https://github.com/pjebs/vite-issue-19186

See file: src/lib/x.ts, src/lib/Counter.svelte and src/App.svelte.

Dev server

Prod code:
You will notice I lose the calling function file information (name and path during development)

[pjebs]

It would be awesome if some kind of solution can be found without source maps.
Sourcemaps are simply too large. It would be awesome to mark only a few files that are relevant to me.

[pjebs]

Alternative an option to produce very limited sourcemaps so only relevant files (in my case only their filenames for a few source directories) can be mapped to reduce the size of the generated sourcemap.

[hi-ogawa]

It sounds like you're proposing an entire source map alternative and that's probably out-of-scope for Vite. Let me close this and it might be possible tackle #19187 instead.