-
Notifications
You must be signed in to change notification settings - Fork 86
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
Remove Object.assign fallback #25
Conversation
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 -- We explicitly haven't supported anything under node@4
for a while. Thanks for the patch!
I just want to throw out that I wish this had been done as a new major version. The 2.x release of this package was out during the lifetime of 0.12, so it's not unreasonable to assume that people were expecting only features compatible with that would be in use. I'm all for dropping support for old versions, but it still seems like a semver-breaking change, even if the older environments are out of LTS. We can no longer build Babel 6 because a sub-sub-dependency uses this package, and Babel 7 is the first release that will be dropping support for 0.10 and 0.12. |
Node 4+, like
.travis.yml
is configured to test.This is useful to keep the browserified bundle size down by excluding a package/method that is no longer used anywhere (
util/_extend
)80KB -> 58KB (28%)
standard@10.0
also includes this suggestion: