Closed madarche closed 8 years ago
According to my https://www.npmjs.com/package/object.assign tests, node 4 has 9 test failures, and node 5 has 8. Native support isn't the same thing as compliant native support.
This note should indicate a) that Object.assign
does not offer "deep extend" functionality, and that b) the native implementations of Object.assign
in both node and many browsers (since npm modules are for the browser too) are not fully spec-compliant. It'd be nice to also point at the object.assign
module for a compliant replacement.
Thanks very much @ljharb I'll modify the PR. Object.assign
in Node.js is working for my usages, I haven't done a compliant native support full review.
(as to the test failures, a rebase on the latest master will fix those, they're obviously unrelated to this PR)
Please @ljharb what do you think of this PR now?
@madarche Thanks! If you could condense these down to 1 commit I'll merge it straight away
@ljharb done as you requested
Since Node.js >= 4,
Object.assign
now offers the same functionality natively. See ECMAScript 2015 (ES6) in Node.js