Could you add Node 5.1.0?

[martinotten]

As of now the release of Node 5.1.0 is stable, even though it has no LTS. Could you please add it to the manifest?

[cf-gitbot]

We have created an issue in Pivotal Tracker to manage this. You can view the current status of your issue at: https://www.pivotaltracker.com/story/show/108744164.

[flavorjones]

Hi, we've received little-to-no feedback on support for node 4.2.x, and so I'm hesitant to add more versions based on the statically-linked-openssl-1.0.2 strategy described in #32.

Have you tried Node 4.2?

[martinotten]

Sure, and it works. But we would prefer to develop for the most recent stable version and have all features available.

[cloudlena]

I couldn't agree more with @Mobbit. Also, many of our users hadn't specified the node engine version in their package.json which lead to them getting errors upon pushing which they didn't understand because the buildpack was trying to download the latest stable version (5.1.0) but couldn't find it...

[voelzmo]

I guess the version resolver shouldn't come up with a version which is not supported by the buildpack? As long as engine is not a mandatory field, it should probably just work(tm) to push an app without that property.

[Dannyzen]

Hi, we're planning supporting 5.1.1 in the next release which should roll out today