Ideas: `versionGuard`, multiple instances of bitcore-lib

braydonf commented 8 years ago

Consolidating/moving issues related to versionGuard:

Include more details in versionGuard message (https://github.com/bitpay/bitcore/issues/1328)
Issues with Electron (https://github.com/bitpay/bitcore-lib/issues/61)
Remove versionGuard, or lower to warning (https://github.com/bitpay/bitcore-lib/issues/21)
bitcore-node related issue: https://github.com/bitpay/bitcore-node/issues/308
load library from global in case of conflict (https://github.com/bitpay/bitcore-lib/pull/4)
update bitcore modules to use bitcore as a peerDependency (https://github.com/bitpay/bitcore/issues/1232)

fed-franz commented 8 years ago

This "multiple instances of bitcore-lib" issue should really be avoided. It is extremely hard to solve and it prevents the development of new services. And judging by the number of issues opened because of it, I think it should be given high priority.

levino commented 7 years ago

Please remove the includeGuard.

bitpay / bitcore-lib

Ideas: `versionGuard`, multiple instances of bitcore-lib #67