-
Notifications
You must be signed in to change notification settings - Fork 380
WIP: frontend: router: Add lazy loading of routes for code splitting #1961
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
base: main
Are you sure you want to change the base?
Conversation
Splitting on every route might be an overkill imho, usually it's only needed in components that import big libraries (for example EditorDialog that imports monaco would be good case for lazy loading). Otherwise it'll just generate a lot of small chunks which might negatively impact build time |
Signed-off-by: René Dudfield <[email protected]>
Signed-off-by: René Dudfield <[email protected]>
Signed-off-by: René Dudfield <[email protected]>
Signed-off-by: René Dudfield <[email protected]>
Because they are not used in many modules, and so they should not be loaded all the time by putting them in the common/index. Additionally, this means that the code is only loaded when the pod details route is loaded. Signed-off-by: René Dudfield <[email protected]>
Signed-off-by: René Dudfield <[email protected]>
Signed-off-by: René Dudfield <[email protected]>
Signed-off-by: René Dudfield <[email protected]>
Signed-off-by: René Dudfield <[email protected]>
Signed-off-by: René Dudfield <[email protected]>
This speeds up the development server when making changes. Signed-off-by: René Dudfield <[email protected]>
This works with Windows, because before setting environment variables did not work when using cmd or powershell. Also use nice -19 to speed things up on WSL a lot. Because in a VM it can be twice as slow normally. It's only getting priority when compiling, so that is usually what we want. Signed-off-by: René Dudfield <[email protected]>
Unknown CLA label state. Rechecking for CLA labels. Send feedback to sig-contributor-experience at kubernetes/community. /check-cla |
PR needs rebase. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
The Kubernetes project currently lacks enough contributors to adequately respond to all PRs. This bot triages PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
No description provided.