-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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: Remove from useDispatchWithMap()
#47835
Conversation
[ propName ]( ...args ); | ||
} ); | ||
return Object.fromEntries( | ||
Object.entries( currentDispatchProps ).map( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
currentDispatchProps
is always expected to be an object as per react-redux
's syntax.
Size Change: -1 B (0%) Total Size: 1.31 MB
ℹ️ View Unchanged
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thank you @tyxla! 👍
Flaky tests detected in 6e571d1. 🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/4114533776
|
What?
This PR removes Lodash's
_.mapValues()
from theuseDispatchWithMap
utility of@wordpress/data
. There is just a single use in that component and conversion is pretty straightforward.Why?
Lodash is known to unnecessarily inflate the bundle size of packages, and in most cases, it can be replaced with native language functionality. See these for more information and rationale:
@wordpress/api-fetch
package haslodash
as a dependency #39495We're aiming to reduce the bundle size of
@wordpress/data
since Lodash is over a quarter of its size.How?
We're using
Object.fromEntries( Object.entries().map() )
as a replacement.Testing Instructions
Verify checks are green - changes are covered by tests.