Support Node.js on ChakraCore

[xzyfer]

Add support for node-chakracore. NVM can be used to install nightlys from https://nodejs.org/download/chakracore-nightly/ as outlined in nvm-sh/nvm#1067. However the stable builds are not yet hosted on nodejs.org, in which case there is not yet a reliable solution see https://github.com/jasongin/nvs/blob/master/doc/CI.md#github-api-tokens.

This will help adoption, and stress testing of node-chakracore.

Related
appveyor/ci#1148
nodejs/node-chakracore#136
sass/node-sass#1776
sass/node-sass#1777

[BanzaiMan]

We should wait until nvm supports it fully. As @ljharb said nvm-sh/nvm#1067 (comment), whatever we do now is likely to be incompatible with any possible future support by nvm.

[xzyfer]

I opened this issue in part because the tone of that, and previous discussions, suggest little interesting in supporting other Node builds. Where as newer alternatives like nvs consider alternate builds as first class as well as being x-platform.

I have requested clarification from @ljharb on how to proceed with adding support. He previously expressed concerns around low usage when jxcore support was requested. However without support from services like Travis CI and AppVeyor adoption among package maintainers is being hampered.

By adding support for ChakraCore you're enabling adoption, and experimentation. It doesn't seem fair to leave that choice in the hands of a package maintainer. Sure users can work around this limitation but it's a non-trivial obstacle, and a sign of low-confidence.

It's also worth noting that other popular version manages have refused added support for ChakraCore on similar grounds.

[xzyfer]

Further clarification from nvm suggests a feature is in the works to add a supported workaround.

[stale]

Thanks for contributing to this issue. As it has been 90 days since the last activity, we are automatically closing the issue. This is often because the request was already solved in some way and it just wasn't updated or it's no longer applicable. If that's not the case, please do feel free to either reopen this issue or open a new one. We'll gladly take a look again! You can read more here: https://blog.travis-ci.com/2018-03-09-closing-old-issues

[strugee]

@Stale it is

[BanzaiMan]

I don’t think this is something we will work on to fix, but rather rely on nvm to provide.

[stale]

Thanks for contributing to this issue. As it has been 90 days since the last activity, we are automatically closing the issue in 24 hours. This is often because the request was already solved in some way and it just wasn't updated or it's no longer applicable. If that's not the case, please do feel free to either reopen this issue or open a new one. We'll gladly take a look again! You can read more here: https://blog.travis-ci.com/2018-03-09-closing-old-issues

[xzyfer]

This feature is coming to nvm - nvm-sh/nvm#1828

[BanzaiMan]

Closing as an upstream issue.