Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

404 download when using io.js #245

Closed
trshafer opened this issue Jul 15, 2015 · 5 comments
Closed

404 download when using io.js #245

trshafer opened this issue Jul 15, 2015 · 5 comments

Comments

@trshafer
Copy link

Hey heroku,

I trying to switch to iojs. I purged the cache before the deploy.

my package.json includes this:

{
  "engines": {
    "iojs": "2.3.4",
    "npm": "2.13.0"
  }
}

This is my build result:

remote: -----> Creating runtime environment
remote:
remote:        NPM_CONFIG_LOGLEVEL=error
remote:        NPM_CONFIG_PRODUCTION=true
remote:        NODE_ENV=production
remote:        NODE_MODULES_CACHE=true
remote:
remote: -----> Installing binaries
remote:        engines.iojs (package.json):  2.3.4 (iojs)
remote:        engines.npm (package.json):   2.13.0
remote:
remote:        Downloading and installing iojs 2.3.4...
remote:        Downloading and installing npm 2.13.0 (replacing version 2.12.1)...
remote:
remote: -----> Restoring cache
remote:        Loading 1 from cacheDirectories (default):
remote:        - node_modules (not cached - skipping)
remote:
remote: -----> Building dependencies
remote:        Pruning any extraneous modules
remote:        Installing node modules (package.json)
remote:
remote:        > bcrypt@0.8.3 install /tmp/build_1f691cd190c2d5cd0cdae0c4d890f4b9/node_modules/bcrypt
remote:        > node-gyp rebuild
remote:
remote:        gyp ERR! configure error
remote:        gyp ERR! stack Error: 404 response dowloading http://nodejs.org/dist/v2.3.4/node-v2.3.4.tar.gz

The same happens for hiredis and any other library that runs node-gyp rebuild.

@hunterloftis
Copy link
Contributor

Hmm; can you try not specifying a custom version of npm, and instead just allowing the version bundled with iojs to do its thing?

@trshafer
Copy link
Author

sure.

@hunterloftis
Copy link
Contributor

related to #202

I'll hook up a patch that skips custom npm installs when using iojs.

@trshafer
Copy link
Author

worked great. Thank you. 👍

@hunterloftis
Copy link
Contributor

resolved by #246

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants