I've tried to use Vite with real world application, but as bigger application is, it slower becomes (much slower than webpack).

Reproduction

1. Use Vite with application with for example 100 components.

Issues

1. Loading all components is consuming more than 30 Mb of data. In Firefox when developer tools are open, 2000 requests (modules) slow down really page load and in some time produces more and more memory usage.

2. When I'm changing some part of component no change visible before restart. In create-react-app it's seen in a second without restart.

3. Every refresh takes much amount of browser's memory, and browser use much more resources.

4. Mobx refreshes are not properly handled, sometimes state changes doesn't make rerender.

5. Even after removing most of the application and leaving only some minimal part reload is faster but still slower than in webpack by the eye.

6. Performance of refreshes depends of that developer tools are open or not.

This bug aims only to point you to some real world problems which in my opinion should be handled to make it more usable.
I understand also that it can be not a "drop in replacement" for webpack, but then correct architecture of application should be briefly explained.

It's a good idea but needs improvement.

System Info

Newest Vite, node 14. 3.5 Ghz CPU, 32Gbytes of ram.