-
Notifications
You must be signed in to change notification settings - Fork 836
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
lodash merge #1928
Comments
Perhaps use edit: actually merge-deep has its own dependencies so it might not be the way to go. |
merge-deep is quite old but it looks very solid and is used widely, we should probably give it a try. |
https://www.npmjs.com/package/extend is another alternative in the case of merging configs, and it has no dependencies ( merge-deep depending on 3 other packages makes it larger once bundled). |
Looks like this (~23k) is smaller than |
merge-deep is the smallest, you have size on npm |
8.46 doesn't include dependency its just the size of unzipping the tar.gz These sizes are pure install sizes with dependencies no tree shaking or bundling.
|
If you check
Counting together 9088 Bytes not sure how did you come out with 288kB. |
From the Github file size stat of https://github.com/justmoon/node-extend/blob/main/index.js the single file package 'extend' (no dependencies) has its size as 3.28KB, which sounds kinda smaller than 'merge-deep' but not significant anyway. |
Personally, I prefer to use something which doesn't have its own dependencies to keep our dependency tree as small as possible. |
Closing as the dependency on lodash.merge has been removed from the code base. |
Just bundled today some web project ( 3 plugins, collector exporter, zone.js, ) and I see something like this
Seems a lodash merge is quite big, I thought it should be much smaller, especially that we only use it for merging config, but it looks like there is just one file and it is quite big.
The text was updated successfully, but these errors were encountered: