The advantage of using this tool would be that you can do a page-refresh on a single page and see how much that specific page can gain from code-splitting and lazy loading.
Then you have not understood the concept properly. It is not like "variable is delcared but not defined."
It is saying that you current page actually requires 20% of the code but is actually loading 100%.
So what you can do is lazily load few modules based on the user events which will give faster initial loads to your application.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
@varunprashar5 Does not seems very optimized way to find used code. Linters can do better job.
The advantage of using this tool would be that you can do a page-refresh on a single page and see how much that specific page can gain from code-splitting and lazy loading.
Exactly 100% correct. So your 10 MB bundle will not be required on your home screen but may be only 100 KB.
Then why not split the code in such a way in first place only.
This can not realistic to be done in first place. You will first diagnose and then act on it. Thats why refactoring phase is there.
Then you have not understood the concept properly. It is not like "variable is delcared but not defined."
It is saying that you current page actually requires 20% of the code but is actually loading 100%.
So what you can do is lazily load few modules based on the user events which will give faster initial loads to your application.