Outdated version exists in npmjs.com? "node-rdkafka": "^2.1.1" install fails (both under npm and yarn)

[d-sphinx]

Hello, everyone! Create a simple package.json:

{
"name": "Test",
"version": "0.0.1",
"dependencies": {
"node-rdkafka": "^2.1.1"
}
}

Installation process will fail under both npm and yarn packet managers.

If i do manual git pulling (including submodules) from here and then yarn it - it's OK, everything compiles, but in a real life when i have to use package.json it doesn't work.

I decided to compare files downloaded from this repo and npmjs (yarn), and they are different!

Differences exist even in *.js files, for example consumer.spec.js:

Why? Is the packet currently available at npmjs outdated?

[matthax]

The currently published version on NPM doesn't support windows. Support was just recently added by #248

You can just do npm install Blizzard/node-rdkafka --save in the meantime. That will tell npm to pull from the repo, not from npm.

[ancashoria]

I'm also unable to install node-rdkafka because of this error:

SOLINK_MODULE(target) Release/node-librdkafka.node
ld: library not found for -lcrypto
clang: error: linker command failed with exit code 1 (use -v to see invocation)
make: *** [Release/node-librdkafka.node] Error 1

I'm using MacOs

npm install Blizzard/node-rdkafka also fails

[webmakersteve]

This is because the crypto search path. I am making an adjustment to the ld search paths so this doesn't happen anymore.

[webmakersteve]

I have made the change to crypto in the search path. And this thread has a few different issues, but I believe they are all resolved. So... closing! Re-open if I'm wrong :)