Node-rdkafka: dyld: lazy symbol binding failed: Symbol not found

[meierval]

Environment Information

• OS [Mac Mojave]:
• Node Version [10.13.0]:
• NPM Version [6.4.1]:
• C++ Toolchain [e.g. Visual Studio, llvm, g++]:
• node-rdkafka version [2.4.2]:

Steps to Reproduce
export CPPFLAGS=-I/usr/local/opt/openssl/include
export LDFLAGS=-L/usr/local/opt/openssl/lib
npm install node-rdkafka
npm install
npm start

[email protected] start /Users/myuser/Documents/projects/myproject
electron .

dyld: lazy symbol binding failed: Symbol not found: __ZN2v816FunctionTemplate3NewEPNS_7IsolateEPFvRKNS_20FunctionCallbackInfoINS_5ValueEEEENS_5LocalIS4_EENSA_INS_9SignatureEEEiNS_19ConstructorBehaviorENS_14SideEffectTypeE
Referenced from: /Users/myuser/Documents/projects/myproject/node_modules/node-rdkafka/build/Release/node-librdkafka.node
Expected in: flat namespace

dyld: Symbol not found: __ZN2v816FunctionTemplate3NewEPNS_7IsolateEPFvRKNS_20FunctionCallbackInfoINS_5ValueEEEENS_5LocalIS4_EENSA_INS_9SignatureEEEiNS_19ConstructorBehaviorENS_14SideEffectTypeE
Referenced from: /Users/myuser/Documents/projects/myproject/node_modules/node-rdkafka/build/Release/node-librdkafka.node
Expected in: flat namespace

node-rdkafka Configuration Settings

Additional context
Electron project, with only "const kafka = require('node-rdkafka')"

[webmakersteve]

I haven't used any of this in electron, but the symbols mentioned seem like core symbols in node. This could happen if the version you compiled for is linking against different symbols at run time than you expect, which may be something to do with how Electron runs node in its embedded engine.

I would start there - sorry I can't be of any more help.

[paulirish]

(There's a bunch of tickets like this.... )

But here's what I noticed.

The node_modules path mentioned in my own error message didn't appear to belong to the VSCode paths. In your example it's /Users/myuser/Documents/projects/myproject/node_modules/node-rdkafka/build/Release/node-librdkafka.node

I changed a symlink that was taking over resolution of node_modules fairly globally. And as a result, this seemed to work.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

[klesgidis]

Hey guys, any update here? It seems that I have the same issue