Web: Cache-able code splitting, Tree Shaking and Routes grouping
Currently Flutter for web build command generates a big single Javascript file in release mode. It is proposed that new routing APIs should allow groping of related routes and then the build command should generate separate Javascript files for each group of routes these files can than be pre-fetched separately. This will help to improve Time to Interactive TTI score and defer or remove unnecessary JavaScript work that occurs during initial page load.
Posted by ansarizafar on Feb 5, 2020, 3:52 PM
Tags
Related issues
- struct's lifetime requirements can be bypassed via covariant field assignment
- Proposal to Reorganize the Moderation Team and Review Moderation Policies
- Progressive FPS degradation appears to be related to dota2.com — blocking the domain prevents the performance loss
- proposal: container/...: generic collection types
- Better Custom Endpoint BYOK
- A concrete policy for backward compatibility until Godot 5.0
Raise real-world problems, find people facing the same issue, and discuss solutions.3,500 issues0 comments
github (Other)
struct's lifetime requirements can be bypassed via covariant field assignment
Proposal to Reorganize the Moderation Team and Review Moderation Policies
Progressive FPS degradation appears to be related to dota2.com — blocking the domain prevents the performance loss
proposal: container/...: generic collection types
Better Custom Endpoint BYOK
A concrete policy for backward compatibility until Godot 5.0
New MTP models not supported
Tracking: 429 / Capacity Issues
Web: Cache-able code splitting, Tree Shaking and Routes grouping
Currently Flutter for web build command generates a big single Javascript file in release mode. It is proposed that new routing APIs should allow groping of related routes and then the build command should generate separate Javascript files for each group of routes these files can than be pre-fetched separately. This will help to improve Time to Interactive TTI score and defer or remove unnecessary JavaScript work that occurs during initial page load.
Comments (0)
No comments yet. Start the discussion.