Include more details in versionGuard message

[braydonf]

A few things that could be helpful:

• The locations of the conflicts (and relevant modules)
• Link to documentation on how to setup symlinks for development purposes
• Link to documentation about peerDependency-like dependency structure (see below)

Correct:

dependencies: {
  "bitcore-lib": "^0.13.7",
  "bitcore-ecies": "^1.0.2",
  "bitcore-payment-protocol": "^1.0.2",
  "bitcore-mnemonic": "^1.0.2",
  "bitcore-node": "^0.2.5",
}

Incorrect:

dependencies: {
  "bitcore-ecies": "^1.0.2",
  "bitcore-payment-protocol": "^1.0.2",
  "bitcore-mnemonic": "^1.0.2",
  "bitcore-node": "^0.2.5",
}

The above will include bitcore four separate times and lead to errors when objects are passed around between the modules.

• It may also be useful to indicate which version of bitcore is supported via the major version number (currently unused)

Edit: Version numbers

[dabura667]

I used browserify on a module with both bitcore and bitcore-mnemonic as "dependencies". The final js file only had bitcore in there once (0.13.3). But called it multiple times, thus giving the error and failing to load the whole js file into the browser.

I agree that this error message needs to clarify a solution to prevent this.

How would I be able to fix my packages.json to allow me to build in browserify properly?

[braydonf]

Using mocha with the --watch flag will have a similar issue, as the index.js is loaded again however the global state isn't refreshed.

As for the browserify issue, you may be able to use --external bitcore --external bitcore-mnemonic in the browserify command similar to how the submodules are browserified: https://github.com/bitpay/bitcore-build/blob/master/index.js#L106

[braydonf]

Also as note, npm find-dupes bitcore-lib is useful for finding duplicates.

[braydonf]

Moved to: bitpay/bitcore-lib#67