@mınxomaτ TIO has two Node versions: the system package (6.12 LTS), and a manual install in /opt (8.5.0). I added the latter to PATH and it prints hello now.
@Downgoat Done. I installed babel-preset-env instead of babel-preset-esXXXX, because that's what npm told me to do.
@Downgoat I avoid adding extra flags whenever I can. I've enabled command-line options for Babel Node though, so you can add whatever flags are pertinent.
@Οurous Looks like Clean tries to build the libraries on first use. That's not possible, as the sandboxed compiler cannot make changes outside the home directory. I'll try to compile them during the installation process.
The issue is that clm tries to recreate/modify the abc files, even if they already exist. One solution would be to copy everything from /opt/clean into the home directory, but I'd like to avoid that.
OK, compiling everything in /opt/clean/lib once doesn't make a difference (can't create abc files), compiling twice changes the error (can't create object files), but compiling thrice appears to make it work. I have no idea why though.
@Dennis thanks again! It needs three runs because it first compiles each file to .abc, then links each module into a full .abc file, then produces the .o files.
@Dennis Oh, actually, it looks like TIO isn't using the iTasks environment for Clean, could you install clean-bundle-complete-linux-x64-latest as a replacement for the current install?
@Dennis The Nightly build is the only release with iTasks, which fixes a lot of bugs with fusion optimisation, has extended import syntax, and allows actually working world-state observation. It hangs because the entire bundle needs to go under the same directory. (Then set to CLEAN_HOME, as per the readme file)