What's New

Node.js Buildpack Updates

Share this post:

What has changed in the Node.js buildpack:

Updated the default Node.js runtime to v0.12.1

If your application doesn’t specify a runtime in its package.json file, your app will now start using v0.12.1, instead of v0.10.x. There’s some services and features on Bluemix that are currently incompatible with v0.12.x.

If you need to use the previous version, specify v0.10.x in your package.json as shown below:

  "engines": {
"node": "0.10.x"
},

The known issues with v0.12.1:

  • When using the Debug Tools feature provided by Bluemix Live Sync, the “Suspend” feature is broken.
  • The mqlight module used for the MQ Light service is not supported on v0.12.x
  • If you find more bugs, let us know on StackOverflow, or dW Answers!

Updated the Node.js runtime to resolve various security vulnerabilities

  • Fixed vulnerabilities in OpenSSL affecting IBM SDK for Node.js. More details are available in the security bulletin.
  • Fixed vulnerability in RC4 Stream Cipher affecting IBM SDK for Node.js. More details are available in the security bulletin.

The latest Buildpack Version is v1.17-20150429-1033.

Developer Advocate

More stories
April 30, 2019

Introducing IBM Analytics Engine v1.2 and Announcing the Deprecation of IBM Analytics Engine v1.0

We are excited to inform you about the new version of IBM Analytics Engine v1.2 that will be available starting May 15, 2019. Along with this release, Analytics Engine v1.0 will be retired.

Continue reading

April 23, 2019

Announcing the Deprecation of the Watson Machine Learning JSON Token Authentication Service

We’d like to inform you about the deprecation of the Watson Machine Learning JSON Token Authentication service. This method of authentication will be retired on May 30, 2019.

Continue reading

April 19, 2019

Introducing IBM Cloud Object Storage Firewall: Further Secure Your Data

IBM Cloud Object Storage (COS) is giving you more control over who can access your data. We have introduced a new capability allowing you to configure your buckets with trusted IP address(es) that will dictate access to the data in COS.

Continue reading