Incorrect stack trace information in dev mode

[pragmasoft-ua]

Describe the bug

In a newly generated vite react-ts application, stack trace information in the error caught by error boundary contains incorrect information, probably due to a wrong sourcemap file.

Reproduction application https://github.com/pragmasoft-ua/remove-vite-app

when run with npm i && npm run dev

produces a screenshot, showing stack trace in both console and error boundary page.

Console shows a valid line number of an error App.tsx:17

Whereas a stack trace in error boundary has an invalid line number

App@http://localhost:3000/src/App.tsx?t=1647602434195:50:19

The problem seems is that the latter one is a line number in a jsx processed file after jsx expansion, whereas line number should be of an original tsx file.

Reproduction

https://github.com/pragmasoft-ua/remove-vite-app

System Info

System:
    OS: Windows 10 10.0.22000
    CPU: (12) x64 Intel(R) Core(TM) i7-8750H CPU @ 2.20GHz
    Memory: 19.78 GB / 31.72 GB
  Binaries:
    Node: 16.13.0 - ~\Applications\node\node.EXE
    npm: 8.1.3 - ~\Applications\node\npm.CMD
  Browsers:
    Edge: Spartan (44.22000.120.0), Chromium (99.0.1150.39)
    Internet Explorer: 11.0.22000.120
  npmPackages:
    @vitejs/plugin-react: ^1.0.7 => 1.2.0
    vite: ^2.8.0 => 2.8.6

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]

I think this is not a bug.
Also it is possible to fix by adding these lines to index.html.

    <script src="node_modules/source-map-support/browser-source-map-support.js"></script>
    <script>sourceMapSupport.install();</script>

[sapphi-red]

Closing as it is not a bug.