merge-deep
merge-deep copied to clipboard
Recursively merge values in a JavaScript object.
There seems to be an issue with this project and https://github.com/vercel/ncc/issues/500, which is cause by the older version of clone deep. This PR upgrades clone-deep to the latest version.
Update clone-merge version for statically analyse, more info: [https://github.com/tdeekens/flopflip/issues/1609](https://github.com/tdeekens/flopflip/issues/1609).
encountered this problem with fresh node_modules bundling with webpack against `[email protected]` relevant issue with recent reports https://github.com/jonschlinkert/merge-deep/issues/4
Bumps [kind-of](https://github.com/jonschlinkert/kind-of) from 3.2.2 to 6.0.3. Changelog Sourced from kind-of's changelog. [6.0.3] - 2020-01-16 Merge pull request #31 for issue #30 [6.0.0] - 2017-10-13 refactor code to be more performant...
Dependencies were updated to fix the [CVE-2019-20149](https://nvd.nist.gov/vuln/detail/CVE-2019-20149) vulnerability keeping in mind about Node >= 0.10 version. The code was fixed according to tests.
Symbols can be used as property keys, but they are ignored. ``` const merge = require('merge-deep'); const mySymbol = Symbol('mySymbol'); const x = { value: 42, [mySymbol]: 'hello' }; console.log(x);...
Can specify which array fields will be replaced (instead of concatenated with `union`). Few lines in code and all tests working. `module.exports = function mergeDeep(orig, objects, notUnionParams) {` ``` if...
Upgrade `clone-deep` to the latest version, so that it [doesn't throw a webpack warning](https://github.com/jonschlinkert/clone-deep/issues/3).
I'm not sure, if this a bug or a feature. Look: ```js import merge from 'merge-deep'; const object1 = { a: '1', b: '2', c: [1, 2, 3] }; const...