1. 4

  2. 14

    They published an update:

    Now that a few days have passed, I should clarify some things.

    At the time I wrote this comment, there was one commit and virtually no discussion on the ayo.js repo. Since then, there’s much more activity, and the goals of the project are much more clear - had this been asked today, I’d not have responded so strongly.

    I still don’t think a fork is the right solution to the issues that precipitated it, but I do wholeheartedly agree with the aims of the fork, and with the morals and values of those who created it - and I fully support their goals.

    In general terms, for a fork to be added to nvm, at a minimum the following would need to be true:

    • there exists at least one official release
    • the project follows semver
    • the project has a way to list versions, preferably identical in format to http://nodejs.org/dist/index.tab and https://iojs.org/dist/index.tab
    • The project ideally provides binaries for at least all the platforms that node supports, and if not, provides a concrete set of rules I can implement to help decide when a user can use a binary or not
    • there exists “enough” interest that the added complexity is warranted (this is a fuzzy requirement, yes, but hopefully it still makes sense to people)

    If anyone wants to make a case for nvm supporting ayo.js, please do, but please note that any anti-CoC or similar trolling will be dealt with promptly.

    quoted from comment by ljharb https://github.com/creationix/nvm/issues/1595#issuecomment-325159240