izaakschroeder/package-merge

Combine `package.json` files intelligently.

package-merge's Issues

lodash version issue

If there is no version of the lodash in package.json, it will use latest, v4.0+ , but, this repo can only use v3.0+.

Error: Cannot find module 'lodash/object/mapValues'
    at Function.Module._resolveFilename (module.js:440:15)
    at Function.Module._load (module.js:388:25)
    at Module.require (module.js:468:17)
    at require (internal/module.js:20:19)
    at Object.<anonymous> (/Users/loye/Documents/coding/FET/cmd2app/node_modules/package-merge/lib/merge.js:5:17)
    at Module._compile (module.js:541:32)
    at Module._extensions..js (module.js:550:10)
    at Object.require.extensions.(anonymous function) [as .js] (/Users/loye/Documents/coding/FET/cmd2app/node_modules/babel-register/lib/node.js:154:7)
    at Module.load (module.js:458:32)
    at tryModuleLoad (module.js:417:12)

Merging "^0.x" and "^0.x" results in "^0.0.0"

Hi,

Got an edge case affecting <1.0 versions of dependencies. We are using your utility to merge a template package.json with a project to standardise dependencies.

When we have a dependency that is under development (e.g. version started at 0.0.1, moving up to 0.1.4 now) we've used '^0.x' to indicate latest pre-release, on a subsequent runs of the merge when both source and dest have the same it results in ^0.0.0 - which doesn't seem to want to install any version!

Also, a workaround of them both being '*' also fails in finding an intersect.

Thanks
Will