Compute Services

Node.js version long-term support and the SDK for Node.js buildpack

Share this post:

By the end of the year we will pass several significant dates on the Node.js long-term support (LTS) schedule:

  • v6 was promoted to LTS status on October 18, 2016
  • v0.10 will reach end of life on October 31, 2016
  • v0.12 will reach end of life on December 31, 2016.

What does this mean for Bluemix?

The default version for the SDK for Node.js, which is used when you do not specify a version in your app’s package.json file, will change from v4 to v6. Node.js v6 delivers many improvements over older releases over older releases, including better performance.

Additionally the buildpack will no longer bundle v0.10 and 0.12 of the SDK for Node.js binaries. While we recommend that you no longer use v0.10 or v0.12 after they reach end of life, if you request v0.10 or v.012 in your app’s package.json file, it will instead download the community version from during staging. In addition to issues related to using a version at end of life (no security updates, etc.), the additional download will slow down staging and adds a dependency on an external site affecting reliability.

What you should do

If your app is still using v0.10 or v0.12, start thinking about migrating it to v4 or (preferably) v6. Specifying a Node.js major version in your app’s package.json file is also a great way to eliminate any surprises as the buildpack evolves. For example:

"engines": {
"node": "4.x"

Specifying the major version of 4 keeps your app on the v4 release where there will be minimal breaking changes, but allows it to pick up new minor versions every time the app is restaged.

More stories
April 19, 2019

Kubernetes Deployments: Get Started Fast

I'm excited to bring you guys a new video format that is going to take a deeper dive on Kubernetes deployments.

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

April 18, 2019

Bring Your Own ALB: DNS with Health Checks and SSL Certificates (Beta)

If you've ever wanted to run a web server, an API gateway, an Ingress controller, a Kafka proxy, a service that has a binary protocol like an MQTT service or database, or essentially anything that runs on TCP (or UDP), you can now run it in IBM Cloud Kubernetes Service on a host name.

Continue reading