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
Currently, our build generates one single file that embeds all components, fonts, and utils.
This affects the First Load JS size as it will load the entire library in the first render.
Proposal
Configure rollup to use manualChunks or another approach that splits the code in chunks that can be imported invididually.
Examples in other libraries
I haven't found yet an example
Who does this impact? Who is this for?
This will impact anyone that uses the lib by optimizing how the components are imported.
RFC
Overview
Currently, our build generates one single file that embeds all components, fonts, and utils.
This affects the First Load JS size as it will load the entire library in the first render.
Proposal
Configure rollup to use
manualChunks
or another approach that splits the code in chunks that can be imported invididually.Examples in other libraries
Who does this impact? Who is this for?
This will impact anyone that uses the lib by optimizing how the components are imported.
Additional context
Rollup documentation around code splitting and manual chunks.
The text was updated successfully, but these errors were encountered: