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 #1044

Closed
jimmywarting opened this issue Oct 16, 2018 · 2 comments
Closed

Use native Object.assign instead of xtend #1044

jimmywarting opened this issue Oct 16, 2018 · 2 comments

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)
@joehand
Copy link
Collaborator

joehand commented Oct 26, 2018

Yes!

@joehand
Copy link
Collaborator

joehand commented Feb 21, 2019

Okay, getting closer here. The leftover dependencies that use xtend are:

  • dat-json
  • dat-registry
  • subcommand
  • dat-node

And then Dat itself =)

joehand added a commit that referenced this issue Feb 21, 2019
@joehand joehand closed this as completed in c68f2f5 Apr 3, 2019
@joehand joehand mentioned this issue Jul 29, 2019
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