Extension Does Not Work Properly With Vite

I am currently using `react-scripts start` to run my React app. I am able to set and hit breakpoints and everything works as expected. We are switching to using Vite and after updating our build process to use Vite breakpoint debugging has become unusable. Because my code is proprietary, there is no way I can post it as an example, and while I do have a smaller example that exhibits odd debugger issues, I can't get an exact repro for every case.

The issue we are seeing is that after moving to Vite, line numbers that are reported in VS Code when hitting an exception are just plain wrong. Like wildly wrong. In other cases we will set a breakpoint in a file and the debugger will stop on a completely unrelated line. In other cases the debugger will simply stop at phantom breakpoints.

Before I go through the arduous process of creating an example repo in github or something to try to create a project that reproduces these issues, can someone confirm whether this is a known issue and has a work-around? Or if anyone else is experiencing this?

To confirm. switching back to `react-scripts` everything works as expected, but using Vite, breakpoints don't work consistently.

Non viene indicato alcun file del repository né alcun test. Inizia con l’esempio Vite più piccolo menzionato nell’issue e confronta il comportamento dei breakpoint con react-scripts in VS Code; per procedere sarebbe necessario un caso riproducibile che documenti righe errate, arresti non correlati o breakpoint fantasma.

Scritto dal modello di indicizzazione a partire dal testo della issue.