You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using Electron, the symlinking strategy will still load bitcore-lib multiple times, and will throw an error from the versionGuard.
Here is the dependency and file structure to reproduce:
app.js
index.js (<- requires bitcore-lib and bitcore-node)
node_modules/bitcore-lib (<- symlink to ~/bitcore-lib)
node_modules/bitcore-node (<- also requires bitcore-lib)
node_modules/bitcore-node/node_modules/bitcore-lib (<- symlink to ~/bitcore-lib)
node_modules/electron-prebuilt
package.json
require('bitcore-lib') with Electron will load bitcore-lib again even though it's a symlink, this is different than when using Node.js alone, likely because the cached path is in reference to the symlink instead of the final path.
When using Electron, the symlinking strategy will still load bitcore-lib multiple times, and will throw an error from the
versionGuard.Here is the dependency and file structure to reproduce:
require('bitcore-lib')with Electron will loadbitcore-libagain even though it's a symlink, this is different than when using Node.js alone, likely because the cached path is in reference to the symlink instead of the final path.