Throwing node version error
See original GitHub issueEnvironment Information
- OS: Ubuntu
- Node Version: 8.9.3
- node-rdkafka version: 2.7.1
When trying to install node-rdkfka
it’s giving me below error:
00:09:15 error node-rdkafka@2.7.1: The engine "node" is incompatible with this module. Expected version ">=12.0.0". Got "8.9.3"
Does NodeJS dependency has changed?
If NodeJS dependency is >=12.0.0
, can we use Openssl 1.1.X
?
As in documentation I still see requirement Node.js >=4
Issue Analytics
- State:
- Created 4 years ago
- Reactions:7
- Comments:6
Top Results From Across the Web
Throwing an error in node.js - javascript - Stack Overflow
Generally speaking, throw is a synchronous method to handle errors. When using callbacks, it's assumed you're dealing with async code where throw isn't...
Read more >Node.js Error Handling Best Practices: Ship With Confidence
Want to ship your Node.js applications with confidence? Learn Node.js error handling best practices, tips and tricks with our simple guide.
Read more >Errors | Node.js v19.3.0 Documentation
Node.js generates system errors when exceptions occur within its runtime environment. These usually occur when an application violates an operating system ...
Read more >15 Common Error Codes in Node.js and How to Fix Them
The ETIMEDOUT error is thrown by the Node.js runtime when a connection or HTTP request is not closed properly after some time.
Read more >Troubleshooting Node.js Deploys - Heroku Dev Center
Check out this advice to troubleshoot failed Node.js deploys. ... internal/modules/cjs/loader.js:960 throw err; ^ Error: Cannot find module ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Based on a blame, pull #610 introduced this field, and it seems like the authors thought it was advisory.
In the meantime, you can usually ignore this e.g.
yarn install --ignore-engines
.This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.