-
Notifications
You must be signed in to change notification settings - Fork 416
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Investigated on bundle sizes( too high) and memory usage during build #4297
Comments
|
@offtherailz you were talking about https://www.npmjs.com/package/babel-plugin-lodash but maybe we can generalize it with https://www.npmjs.com/package/babel-plugin-import |
I would First do an ordered list of libraries by size. Then evaluate effort to remove for the Firsts in list. I would start removing the ones on top with the less effort to remove. |
Here reporting the npm run analyze with examples
Here reporting the npm run analyze without examples
|
It is really problematic .. We try to use it and deploy with CICD on gitlab but we need to add Have you find a solution? Thanks in advance |
#6622 and #6621 should reduce from 12Mib to around 9Mib the main bundle size. We can then procede optimizing:
module.exports = function(api) {
api.cache(true);
return {
"presets": [
"@babel/env",
"@babel/preset-react"
],
"plugins": [
["transform-imports", {
"react-bootstrap": {
"transform": "react-bootstrap/lib/${member}",
"preventFullImport": true
},
"lodash": {
"transform": "lodash/${member}",
"preventFullImport": true
}
}],
"@babel/plugin-proposal-class-properties",
"@babel/plugin-syntax-dynamic-import"
]
};
};
TODO: see the effective uglified sizes in production. |
I changed the milestone, all the optimization are on the 2021.02.00 now. |
As a final report of the current operation we can compare stable with master the bundle size (main bundle) decreased of 23%, 15% gizipped. (~3MB to ~2.5MB transferred), that is not enough for a visible improvement in terms of page load The analysis from lighthouse will port to create a second issue #6735 |
…ct-data-grid-addons (geosolutions-it#6692)
…ct-data-grid-addons (geosolutions-it#6692)
We should investigate and propose solutions to:
The text was updated successfully, but these errors were encountered: