Does anyone know of a NodeJS Redis client compatible with NodeJS version 4.8.xish?
I have tried node-redis and ioredis both and have ran into issues.
The Node.js Redis client is generally compatible with Node.js version 4.8.x, but the specific version of the client you are using may have different requirements.
It's worth noting that Node.js 4.8.x is an old version, it reached its end-of-life on April 30th, 2018, and it's recommended to use a more recent version of Node.js for your application.
It is also important to check if the Redis server version you are using is compatible with the Redis client library you are using.
If you are using an old version of the Redis client library, you may encounter issues with compatibility. In this case, it's recommended to upgrade to a more recent version of the library.
Related
Meteor is typically behind in Node.js version because it is a framework that uses its own bundled version of Node.js, and its APIs and features are built to rely on that version of Node.js.
I'm sure that in many cases upgrading Node.js poses no problem.
As an example, Meteor 2.10 at time of writing ships with Node.js 14. But we're already on Node.js 19.
Is there a way to tell Meteor (f.e. with the meteor cli, or some meteor package) to use newer versions of Node.js (and npm)?
Meteor 1.4 now supports Node 4.4.7!
See release notes
To upgrade to Meteor 1.4:
Go to the root of your project's directory
meteor update
Meteor does not support NodeJS 4+ as of now. The discussion is available in https://github.com/meteor/meteor/issues/5124
The latest update to the thread on April 29 is:
Guys, relax. The difference between Node version 4, 5 and 6 are relatively minor, and so if Meteor can support one, it can and will support all others. Ben created PRs for every currently active and supported Node version, but the fundamental part of the work is about making Meteor work with any (recent, non-legacy) Node version, and from there basically everyone should be able to freely select whichever one fits their goals and intentions best (i.e. 4.x if you don't care for bleeding edge Node, 6.x if you do; 5.x is not going to stick around for very long as it's not an LTS version).
So come and check out and help with the PRs if you're interested and
you can, but if not, just rest assured this is being worked on and
prioritized appropriately and I'm pretty sure Ben (and/or others
working on this) will keep everyone posted on any meaningful progress.
when I run
node -v
I got 4.2.1 which is very strange since I remember I worked with 0.10 versions: I am totally lost with nodejs versions
reading the pm2 doc
Warning: If you want to use the embedded load balancer (cluster mode),
we recommend the use of node#0.12.0+ or node#0.11.16+. We do not
support node#0.10.*'s cluster module anymore.
I don't understand how node.js versions works: looks like we jumped form 0.10
to 4.2
Does pm2 works with latest version of node.js ?
regards
don't understand how node.js versions works: looks like we jumped form 0.10 to 4.2
When io.js and node.js merged, then node.js jump directly to 4.x series. This happened due to difference in versions of io.js (3.x series) and node.js (0.x series). So next common version was named 4.x series and this lead to some confusion. See this announcement.
Does pm2 works with latest version of node.js ?
You can give it a try yourself, but IMO it should work well.
At the end of 2014, node was forked into io.js for reasons I won't cover here.
The io.js project adopted the semver notation and, as the pace of changes was very fast (we got all the recent advances of ES6 that were already available in V8), came to version 3.
In september 2015, io.js was merged back into node, and it was decided to keep the semver versionning, and to go to version 4. More details here, including the LTS.
This makes it possible to deal with a monotonous version order, thus a 4.0 version of node is greater than a 0.11 version. But be wary, many changes were introduced and the ecosystem is big. You'll probably have changes to do when going from 0.x to a new version, especially if you use many modules.
I've been trying to find the supported versions on node on the expressjs page, but can't find an official list. Has expressjs been updated to work with the newest releases of node?
As of today (Oct 09, 2015), the package.json file on the ExpressJS master branch still mentions that it supports node versions >= 0.10.0, so semantically speaking that would imply node 4.x.
However, there is an open issue dealing specifically with the node 4.x support. The current state is that express devs are trying to find which dependencies might have an issue running on node 4, but so far they've not found any.
So in theory, Express 4 should not have any issues running on Node 4.
I see that Node.js has added i/o to its capabilities, does that mean that it's more async now, or it is using the same concurrency model as before?
Also, I thought Node was on v8, why have they rolled back to v4?
io.js was a fork of the node.js codebase that was advancing differently than the core node.js. io.js was its name and is not directly related to some large set of I/O capabilities.
The version 4.0 nomenclature is derived from the versioning scheme that io.js was using and this is essentially the next major version of that fork. You can read more details in this article: 4.0 is the new 1.0. And, you can read about the merger of the io.js and node.js code bases into the Node Foundation in this article: Node.js and io.js Merge Under the Node Foundation.
All versions of node.js and io.js use the V8 Javascript engine from Google. Those the phrase "V8" implies "version 8", that is not how it is used. "V8" is the name of the Google JS engine and does not change. There is a separate version number for the V8 engine. The 4.0 version number is a node.js version and has nothing to do with which specific version of the V8 JS engine is included.
In this article All you need to know about Node.js 4.0.0, there is this passage which addresses the version number question:
Why “4.0.0”?
The io.js project uses semantic versioning (semver) with its first
major release being a 1.0. The current main line of io.js is 3.x. To
avoid collisions with the 0.x scheme of Node.js it was decided that
the converged version should be a 4.0.0 and will also be following the
semver scheme .. from now on.
Hi I am using the IBM SDK for Node.js 1.1.0.14 , which is based on joyent v0.10.38.
I can use tls.getLegacyCiphers("v0.10.38") or tls.getlegacyCiphers() in
the IBM version of node.js
but I cannot find the same API in the joyent v0.10.38?
Thanks
This is newly added into the IBM SDK for Node.js version only.
The IBM SDK Node.js version 1.1.0.14 has removed the RC4 from the default set of ciphers used for the TLS protocol, to address the Bar Mitzvah security vulnerability
http://www.ibm.com/developerworks/web/nodesdk/javascript_current_news_technote.html
This will be available in the future version of the joyent Node.js.
IBM SDK for Node.js V1.1.0.14 has an early version of the RC4 fix. We have contributed the fix to Node.js and are waiting for Node.js 0.10.39 to become available.