Skip to content

node v4 #2765

@hueniverse

Description

@hueniverse

node v4 is out and you should be pretty excited! There is a lot to love about the new version, both technically and community wise. Between the new v8 engine, the hundreds of bug fixes and improvements, and a responsive core team addressing issues, we want to make sure the hapi.js community can jump right in and take advantage.

Today.

With the exception of some non-hapi-specific edge cases, the core hapi module and every single one of its dependencies have been tested on the new node version and passed successfully. This gives us the confidence to recommend node v4 as the new standard development environment for hapi users.

That said, we recognize that moving from the current official hapi node version of 0.10 to 4.0 is a big deal and can take months in a large enterprise or sensitive production environments. Like any new major release of node, there are likely to be bugs that will only show up at scale. So we don't want to rush anyone into making a move they are not ready for.

hapi v10

Today we are publishing a new major version of hapi - version 10 which is identical to the last version published (v9.3.1). We are doing so to enable us to immediately take advantage of new node and JS APIs available in node v4 without having to confuse hapi API changes with node dependencies. If you are currently using hapi v9, you can immediately switch over to v10 after moving to node v4.

We expect to release a few hapi v10 releases over the next few weeks using some of the new JS features such as const, let, and Promises for APIs currently requiring callbacks. These will be patch and minor releases.

hapi-lts

We are also announcing today an LTS hapi brach available under the @9.x.x versions. The LTS branch will continue to include hapi v9 releases for current node v0.10 users. We will do our best to port as many important security bug fixes from the master branch. The LTS releases will continue to support node v0.10 until June 2016.

The LTS distribution is led by Nathan LaFreniere and sponsored by &yet.

Metadata

Metadata

Assignees

Labels

breaking changesChange that can breaking existing codeltsBackport for maintained old version

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions