You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Modify webpack config and react routing code to allow split finish bundle into the chanks by routes. Webpack will generate separate bundles for each of the route. And app will lazy loading needed modules by visited route. Example: If we visit transactions tab we don't need to load explorer relative modules and etc.
This will improve load performance, especially for mobile devices.
This issue relative to #509
Actual behaviour
Lisk Hub shipped to a user as a single code bundle.
Steps to reproduce
Visit Lisk Hub.
The text was updated successfully, but these errors were encountered:
I agree this is something we should do at some point, but the benefit won't be huge.
The bundles should be heavily cached (after #514), so code-splitting causes speed up only on the first load.
The biggest part is the cryptography libs (js-nacl, bitcore-mnemonic) and those are needed on login page and authenticating the user to any page that requires logged user.
Expected behaviour
Modify
webpack
config andreact routing
code to allow split finish bundle into the chanks by routes. Webpack will generate separate bundles for each of the route. And app will lazy loading needed modules by visited route. Example: If we visit transactions tab we don't need to load explorer relative modules and etc.This will improve load performance, especially for mobile devices.
This issue relative to #509
Actual behaviour
Lisk Hub shipped to a user as a single code bundle.
Steps to reproduce
Visit Lisk Hub.
The text was updated successfully, but these errors were encountered: