Lock Node version in Heroku Procfile about recycling

[alexkahn]

It looks like Heroku uses the latest stable minor '0.10.x' and the previous stable minor (while we don't have any major). The loose versioning in the package file will probably be most beneficial since they make security updates as they become available. They drop support for previous stables as new minors come out. As far as the Procfile goes, I'm not sure we can specify a node version without something like NVM.

On November 29, 2014 2:17:58 PM EST, Ben [email protected] wrote:

The deprecation warning in issue in PR #46 was likely because we are
using loose versioning in our package.json (0.10.x). I'm developing
using Node 0.10.32, and heroku is periodically deploying newer
versions. We can lock our deployment to a specific node version in the
Procfile. @alexkahn, can you please find out what the current version
of Node is on Heroku and add the appropriate entry in the procfile and
package.json to make sure we keep our dev and production environments
in sync?

---

Reply to this email directly or view it on GitHub:
#47

Sent from my Android device with K-9 Mail. Please excuse my brevity.