Skip to content
This repository has been archived by the owner on Aug 31, 2018. It is now read-only.

Native module builds (node-gyp) expect the tarball to be named "node-…" #37

Open
valpackett opened this issue Sep 1, 2017 · 2 comments

Comments

@valpackett
Copy link

Trying to npm i nodegit with my build

Error: 404 response downloading https://unrelentingbuildbot.s3.dualstack.eu-west-1.amazonaws.com/ayo/v9.0.0-nightly201708257a10dc574
bbbeb6dc45c69f115967f2b17fc90c9/node-v9.0.0-nightly201708257a10dc574bbbeb6dc45c69f115967f2b17fc90c9-headers.tar.gz

I have renamed it in my bucket, but this is going to be an issue for everyone potentially.

Should the build process actually produce ayo-… tarballs or node-…? The latter might be potentially confusing, but should all the existing tooling adapt to the existence of ayo? (I guess there might be a lot of tooling and not all of it might be maintained?) How was this handled in io.js?

@Qard
Copy link
Member

Qard commented Sep 1, 2017

io.js used iojs as the prefix. https://iojs.org/dist/latest-v3.x/

@ljharb
Copy link

ljharb commented Sep 1, 2017

For ayo.js to get nvm support eventually, it will be important to try to do "what io.js did" in just about every question like this. Picking a prefix (like "ayo") would work fine tho :-)

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

No branches or pull requests

3 participants