You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 31, 2018. It is now read-only.
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?
The text was updated successfully, but these errors were encountered:
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 freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Trying to
npm i nodegit
with my buildI 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 ornode-…
? The latter might be potentially confusing, but should all the existing tooling adapt to the existence ofayo
? (I guess there might be a lot of tooling and not all of it might be maintained?) How was this handled inio.js
?The text was updated successfully, but these errors were encountered: