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
We should ensure this library never gets too large by implementing a check against the bundle size. Can potentially do it via inspecting the outputs of webpack-bundle-analyzer but otherwise there are other npm packages that do this
I'm not sure how we can measure this at a component level in this repo. Each component is its own package which means consumers can opt-in to only the components they need. It also means we are not using web-pack any where as this would live at the project level.
Perhaps we can write a script that measures the "file size" of each of the components "lib" folder?
We should ensure this library never gets too large by implementing a check against the bundle size. Can potentially do it via inspecting the outputs of
webpack-bundle-analyzer
but otherwise there are other npm packages that do thisInspired by https://material-ui.com/guides/minimizing-bundle-size/
The text was updated successfully, but these errors were encountered: