dyld: lazy symbol binding failed: Symbol not found

[nornagon]

I'm running this module on OSX 10.6.6, node.js v0.4.1, with bcrypt installed by 'npm install bcrypt'.

When I require('bcrypt'), I get these messages:

dyld: lazy symbol binding failed: Symbol not found: __ZN2v811HandleScopeC1Ev
  Referenced from: /usr/local/Cellar/node-v/0.4.1/lib/node/.npm/bcrypt/0.2.3/package/build/default/bcrypt_lib.node
  Expected in: flat namespace

dyld: Symbol not found: __ZN2v811HandleScopeC1Ev
  Referenced from: /usr/local/Cellar/node-v/0.4.1/lib/node/.npm/bcrypt/0.2.3/package/build/default/bcrypt_lib.node
  Expected in: flat namespace

[nornagon]

Fixed in node 0.4.7.

[ncb000gt]

Huzzah! :)

[durja]

I am using bcrypt 3.0.1 and node 8.9.3 version and I get the error as stated above.

`dyld: lazy symbol binding failed: Symbol not found :__ZN4node19GetCurrentEventLoopEPN2v87IsolateE Referenced from: /Users/local/WebstormProjects/be/node_modules/bcrypt/lib/binding/bcrypt_lib.node
Expected in: flat namespace

dyld: Symbol not found: __ZN4node19GetCurrentEventLoopEPN2v87IsolateE
Referenced from: /Users/local/WebstormProjects/be/node_modules/node_modules/bcrypt/lib/binding/bcrypt_lib.node
Expected in: flat namespace`

[recrsn]

@dujra Try recompiling the addon. npm rebuild bcrypt --build-from-source

[bossley]

@agathver Thank you! This worked for me!

[Gwillison415]

npm rebuild bcrypt --build-from-source

Worked for me as well! thanks!

[andrewaarestad]

This is happening for me with node 8.2.1 and bcrypt 3.0.2. I was able to fix it locally by recompiling as suggested by @agathver but that's not an option for me in production so I had to downgrade bcrypt.

[gastonelhordoy]

This is happening for me with node 8.2.1 and bcrypt 3.0.2. I was able to fix it locally by recompiling as suggested by @agathver but that's not an option for me in production so I had to downgrade bcrypt.

Hey @andrewaarestad, which version of bcrypt worked for you? Thanks man!

[andrewaarestad]

@gastonelhordoy I haven't had any issues after downgrading to bcrypt 3.0.0.

[gastonelhordoy]

Thanks @andrewaarestad, it worked!

[connor11528]

@agathver thanks for the command. Any insight into why running this command fixes the error?

Worked for me using "bcrypt": "^3.0.2" and node v8.9.1. Interested to know what was wrong!

[AndyAlex]

@andrewaarestad I tried downgrading to 3.0.0 but still had the same problem (Node v8.9.4). Running npm rebuild bcrypt --build-from-source worked for me, but that's not a very nice "hack". I'm interested if (and when) this can be fixed. It's not very cool for production environments.

Regards all

[PrajwalKrishna]

npm rebuild bcrypt --build-from-source worked for me as well but can anyone explain me why and how is it working

[recrsn]

@pk1210 There was an ABI incompatibility between 8.X releases. You have to recompile from sources in order to bind to the correct symbols, if you are on the affected versions.

[joch182]

@dujra Try recompiling the addon. npm rebuild bcrypt --build-from-source

Worked for me! Thanks

[Klutch27]

September 2019 and @agathver solution npm rebuild bcrypt --build-from-source worked for me. Not sure why this is the case though? No one else on my team ran into this issue except for me. Thanks for the help!

[Sharat005]

@agathver Worked for me as well! Thanks :)

[FullstackJack]

I forgot to nvm use in a new terminal window. It was installed with a different version of Node than the default system Node.

[Tsourdox]

I just updated node to the latest version 13.x and that solved it for me :)