Skip to content
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

Use native Object.assign instead of xtend #82

Open
jimmywarting opened this issue Oct 16, 2018 · 1 comment
Open

Use native Object.assign instead of xtend #82

jimmywarting opened this issue Oct 16, 2018 · 1 comment

Comments

@jimmywarting
Copy link

xtend can easily be replaced with Object.assign

This reduce the dependencies and possible also avoid duplicated versions where some package don't use the same version range for the xtend package

// immutable
Object.assign({}, a, b)

// mutable
Object.assign(a, b)
@goto-bus-stop
Copy link
Member

I appreciate the commitment but please don't open issues for every browserify package that uses xtend. This module is part of browserify so its appreach will be the same as the main browserify package. Until there is a particularly good reason to drop support for Node < 4 it won't happen. It takes no maintenance effort to use xtend so I really don't see a reason to move away.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants