-
Notifications
You must be signed in to change notification settings - Fork 397
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Trouble Installing node-rdkafka on Node.js v23 #1099
Comments
Bumping this. We are also seeing this issue. Here are the npm error logs.
|
I am running into the same problem with Node v23
|
I am getting an error with Node 23 (node-gyp v10.2.0) on Mac OSX 15.1.0 M3 max chip.
|
I'm using Node v18.20.5 (
|
I'm using Node v18.18.0, installing
|
Had same with 17.9.1, worked for me with Node v16.20.2 |
This project looks pretty dead. I migrated to confluent-kafka-javascript without too many issues. The API is backwards compatible and all you would really need to do is follow the migration guide and change the import package. |
I don't think this project is truly dead, as there was a release just a month ago and the last major release about a year ago. However, the level of active maintenance does seem uncertain. Since node-rdkafka works on Node.js LTS versions but not the latest (v23), I’ll hold off for now and wait for further updates. |
This project has successfully followed librdkafka and Node.js releases for many years. I haven't had a breaking upgrade and have never been blocked when we needed to upgrade (for example when a Node.js LTS has ended its maintenance period). Not upgrading too fast is a way to save time and effort, both for them and for us users. |
Hi, it's great to hear that things are working for you! The reason why I said it looked pretty dead to me was because there are a lot of issues/PRs open, and I don't see that changing any time soon. When I checked the comments, it didn't look like there were maintainers looking at the issues. I just wanted to share that an alternative existed. I am sure you know this already, but Confluent is one of the big backers of Kafka, and they drive Kafka's development. I made the personal choice to switch to using Confluent's library because the upgrade path is currently seamless, and I wanted to be able to use node:22-alpine without needing to compile. |
Installation Issue with node-rdkafka on Node.js v23
Environment Information
Steps to Reproduce
Additional Context
The text was updated successfully, but these errors were encountered: