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.
Related
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.
I have an azure mobile app that is consumed by a Cordova app - this azure mobile app is built in node.js and is responsible for managing the push notifications for this Cordova app.
In this node app, I use mobileservices-sqlserver to register in the database the devices that will receive the push notifications, and I am having problems with this module compilation in node version 6.1.9 - actually any version higher than 0.8x.
Can I pre-compile this mobileservices-sqlserver to a newer node version, maybe using node-gyp? I couldnt find any instructions on how to do that.
Sorry if that is silly question, but I'm really new to node.js.
I've seen some similar issue here, but I'm not sure if it's the same.
Is this an old Mobile Services service? If so, check out the Mobile Apps Compatibility NPM, which replaces mobileservices-sqlserver with the msnodesqlv8 and will allow your service to work with modern versions of Express and Node.js.
If this is already a more modern Mobile App service, see also the mssql NPM for SQL Server data access.
I am using Windows XP and using Sublime Text 3 build 3126. I'd like to use the SublimeLinter framework with it, but they are listing NodeJS as a dependency. How can I ensure that NodeJS is available on my system path?
Prevent node from running and installing on Windows Vista or earlier.
Windows XP and Vista are no longer supported
Launching the msi, with Windows Installer 5.0 (it's available as an update)
Launching the msi, with Windows Installer < 5.0
What about Node.js v0.10 and v0.12?
If you're still currently using Node.js v0.10 or v0.12, it is time to begin the transition to v4 or v6. Both v0.10 and v0.12 are considered to be in Maintenance mode currently and will fall off our support plan completely later this year.
What about Node.js v5?
Node.js v5 will continue to be supported for the next two months in order to give developers currently using v5 time to transition to Node.js v6.
if you still want to proceed with xp setting the environment see this link
Setting up HTTP server on Windows with Node.js
Windows XP support has ended
find about latest version here
https://support.microsoft.com/en-us/kb/936929
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.
Starting with AWS-Lambda and the Serverless Framework i am confused about node versions:
The AWS help site says that (on 21-March-2016)
AWS Lambda supports the following runtime versions:
Node.js: v0.10.36
So i did install Node.js v0.10.36 on my local machine. Installing the latest (v 0.4.2) serverless framework via
npm install serverless -g
it gives the following warning:
npm WARN engine serverless#0.4.2: wanted: {"node":">=4.0"} (current:
{"node":"0.10.36","npm":"1.4.28"})
I thought having the same version locally as on AWS might help having a consistent development environment... Am i wrong? What Node.js version should i run locally to get the most out of serverless?
The Serverless Framework requires Node.js v4.0 or higher. Any version of Node.js within the v4.x or v5.x lines should work.
You are correct that AWS Lambda currently only supports Node.js v0.10.36. The decision to build the Serverless Framework on Node.js v4.0 was done in anticipation that AWS Lamabda would eventually support Node.js v4.0 or higher.
When developing code for AWS Lambda, you should continue to only use features compatible with Node.js v0.10.36. If you make any contributions to the framework, you can use Node.js features available in v4.0+.
Another option is to use Babelify to transform your ES2015 code uploading to AWS Lambda. This allows you to develop in ES2015 without having to wait for AWS Lambda to officially support it. This can be done automatically each time you deploy with the Serverless Framework using the Optimizer Plugin.
Update: A new option now exists, the Serverless Babel Runtime. This goes one step beyond what Optimizer does, and uses Babel inside the runtime itself.
Update 2: AWS Lambda now supports Node.js v4.3.
If you are starting out with a brand new, fresh project I would highly avoid starting with node 0.10.x. That version is just receiving important security fixes at this point, and only for another five months (until October 2016).
The Node.js has adopted the common Long Term Support (LTS) pattern to keep releases timely and stable. Here is the current LTS plan for node.
I would highly recommend starting out with version 4 or 5, depending on your appetite for change and keeping your project up to date. You will be able to take advantage of numerous new features over the 0.10/0.12 releases as well as better prepare you for ES6.