TAtarr11·Sep 7, 2017
Looks like its still having problems on Heroku
https://github.com/heroku/heroku-buildpack-nodejs/issues/468
In Yarn 1.0: Workspaces, auto-merging lockfiles, selective versions resolutionsheroku
heroku-buildpack-nodejs
Shell2012–2017
heroku / heroku-buildpack-nodejs
heroku-buildpack-nodejs
Heroku's classic buildpack for Node.js apps
8Distinct people
8Mentions
0Explicit recommenders
1.3KGitHub stars
What to know before exploring
What it is
Heroku's classic buildpack for Node.js apps
GitHub
Where it is used
No documented product use has been verified yet.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by year8 dated mentions
Observed mentions: 2012-01-20 00:37:01 UTC to 2017-09-07 19:40:16 UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2012 | 2012-01-01 00:00:00 UTC | 2013-01-01 00:00:00 UTC | 3 | 0 | 3 |
| 2013 | 2013-01-01 00:00:00 UTC | 2014-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2014 | 2014-01-01 00:00:00 UTC | 2015-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2015 | 2015-01-01 00:00:00 UTC | 2016-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2016 | 2016-01-01 00:00:00 UTC | 2017-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2017 | 2017-01-01 00:00:00 UTC | 2018-01-01 00:00:00 UTC | 1 | 0 | 1 |
What Hacker News says
8 sourcesIt sounds like you'd want to lock to a specific version of the java buildpack, before 94276a, which dokku supports, according to the docs provided in the GP comment:
> You may also wish to use a specific version of a buildpack, which is also simple
# using v87 of the nodejs buildpack
# replace APP with the name of your application
dokku config:set APP BUILDPACK_URL=https://github.com/heroku/heroku-buildpack-nodejs#v87
http://dokku.viewdocs.io/dokku/deployment/buildpacks/
In The Dokku TrapHeroku's way ahead of you... https://github.com/heroku/heroku-buildpack-nodejs/blob/a77cd...
EDIT: To clarify, though I haven't tried it myself, it looks like you can just specify `"engine.iojs": "1.0.0"` in your package.json, and Heroku will install the entire io.js system for you.
In Io.js 1.0.0Great, thanks. I also figured out that I could put the following line into a file called `.env` (I was originally trying to use a file named `ENV`):
export BUILDPACK_URL=https://github.com/heroku/heroku-buildpack-nodejs
This will use Heroku's version of the build pack, which already has a fix for the NPM problem.
In Npm's Self-Signed Certificate is No MoreYeah I think that's a relic of their very early Node.js beta. Now they look for package.json (https://github.com/heroku/heroku-buildpack-nodejs/blob/maste...) and you define the command to start the app in the Procfile.
In How Heroku WorksYes, nice post. There is some neat stuff in Heroku like buildpacks, but they are also very specific to Heroku, which is a big downside. I really think it is a shame they didn't just use a standard packaging system like .deb to handle things. The server instances are already Ubuntu... it seems like a natural extension to just support setting up a list of .deb files to load into an instance and have it 'just work'.
I needed recent ImageMagick/Ghostscript binaries and I spent many hours trying to get Vulcan to work and finally gave up. It is a mess and not documented very well. Someone commented on your blog that they've moved to another system (anvil) to deal with compiling binaries. I can see why they did this... so much unplanned stuff was bolted onto Vulcan it finally just stopped working entirely. It ended up being easier to just write
Read the rest
a shell script, but this certainly isn't as sexy as using Vulcan or just installing a source .deb. https://github.com/lookfirst/convert/wiki/Compile
ddollar seems like a very smart, but very busy guy. Relatively simple issues are getting dropped on the floor. https://github.com/heroku/heroku-buildpack-nodejs/issues/20 It would be nice if he got some more help from within Heroku.
Anyway, thanks for writing your tutorial... more documentation is always good.
The node.js buildpack has good instructions for how to upgrade it yourself if needed: https://github.com/heroku/heroku-buildpack-nodejs (and the buildpack docs are now public since Heroku's Cedar stack became the official default)
In Node.js v0.8.0 [stable] is outAnd a link to Heroku Buildpack: https://github.com/heroku/heroku-buildpack-nodejs
In Running Your Own Node.js Version on Heroku