Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issues with real world app - slow refresh, rendering parts. #3208

Closed
michalzubkowicz opened this issue Apr 29, 2021 · 3 comments
Closed

Issues with real world app - slow refresh, rendering parts. #3208

michalzubkowicz opened this issue Apr 29, 2021 · 3 comments

Comments

@michalzubkowicz
Copy link

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.

@aleclarson
Copy link
Member

This isn't actionable unless you provide a reproduction. Closing for now.

@michalzubkowicz
Copy link
Author

I've mentioned issues, they are problematic design flaws, if after 4 months is everything you can say is "closing for now" it doesn't encourage me to do something with that either :)

@aleclarson
Copy link
Member

Use Vite with application with for example 100 components.

This is not a valid reproduction. It does not prove any of your proclaimed "design flaws".

Perhaps, if these were inherent flaws in Vite, this issue would have much more attention.

Anyway, I will reopen if you add a git repo with instructions to reproduce. ^^

@github-actions github-actions bot locked and limited conversation to collaborators Oct 4, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants