Push rejected with compilation error

[bkeepers]

I don't have time to investigate right now, but my deploys to heroku started failing this morning with:

-----> Building runtime environment
/tmp/buildpack_c475cde4-d577-4a04-a126-7e833f50343c/bin/compile: line 255: [: too many arguments

Full log: https://gist.github.com/bkeepers/83e90fa55fba0dc91f06

[searls]

Do you recall which time?

On Wed, Jul 2, 2014 at 9:00 PM, Brandon Keepers notifications@github.com
wrote:

I don't have time to investigate right now, but my deploys to heroku started failing this morning with:

-----> Building runtime environment
/tmp/buildpack_c475cde4-d577-4a04-a126-7e833f50343c/bin/compile: line 255: [: too many arguments

Full log: https://gist.github.com/bkeepers/83e90fa55fba0dc91f06

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

[searls]

The only recent change was merging in @mdoel's PR #26

It'd be super helpful if you could set your build pack to a prior ref and see if it was introduced by the PR.

On Wed, Jul 2, 2014 at 9:00 PM, Brandon Keepers notifications@github.com
wrote:

I don't have time to investigate right now, but my deploys to heroku started failing this morning with:

-----> Building runtime environment
/tmp/buildpack_c475cde4-d577-4a04-a126-7e833f50343c/bin/compile: line 255: [: too many arguments

Full log: https://gist.github.com/bkeepers/83e90fa55fba0dc91f06

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

[bkeepers]

No clue why it just started failing, but apparently it's because I have all the lineman deps listed as devDependencies:

Heroku only installs production dependencies by default (this must have just changed in the last week or two), but you can override that with:

$ heroku config:set npm_config_production=false

Would it make sense to do this by default in the lineman buildpack, since it calls npm prune --production in the compilation process?

[searls]

Reopen please. I think you're right. Since we call npm ourselves from a shell script I'm confused how Heroku could have broken us. Nevertheless we should be able to force npm to install Dev deps

On Sun, Jul 6, 2014 at 11:12 AM, Brandon Keepers notifications@github.com
wrote:

Closed #27.

Reply to this email directly or view it on GitHub:
#27 (comment)