[MGNLFE-80] Code-splitting in SPA Created: 07/Oct/20 Updated: 07/Oct/20 |
|
| Status: | Open |
| Project: | Magnolia Frontend Helpers |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Story | Priority: | Neutral |
| Reporter: | Christopher Zimmermann | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
| Description |
|
As a developer, I want the frontend-helpers libraries to support code-splitting so that the SPA can load faster and use less bandwidth Context Currently code-splitting is not supported which means that all components that are used in the SPA are loaded in the first load of the app which makes for a heavy load. Ideally only the components needed on a specific page or in a certain section of a website would be loaded. And then the other ones would be loaded when the user goes to that section of the site where they are needed. Resources https://reactjs.org/docs/code-splitting.html https://blog.angular.io/angular-tools-for-high-performance-6e10fb9a0f4a
|