juxt

steveb8n 2017-10-20T07:05:49.000133Z

@stijn I’ve seen that error when the version of nodejs is not correct for Lumo. To fix, check the Lumo repo to find out which version you need, then manually instead the specific nodejs version

steveb8n 2017-10-20T07:06:21.000197Z

I had to address is in my dockerfile, see https://github.com/stevebuik/docker-roll/blob/master/Dockerfile

dominicm 2017-10-20T07:06:44.000034Z

That's an odd fix, lumo bundles it's own copy of node

steveb8n 2017-10-20T07:07:17.000062Z

yes odd indeed. I saw it on my OSX laptop as well as on Alpine linux

steveb8n 2017-10-20T07:07:21.000235Z

fix was the same both times

dominicm 2017-10-20T07:07:23.000265Z

I wonder why it does something to the host node.js

stijn 2017-10-20T08:06:50.000186Z

on os x I don't have the problem, but I do on Archlinux

stijn 2017-10-20T08:41:41.000067Z

hmmm I'm running node 8.7.0

stijn 2017-10-20T08:42:04.000132Z

switching to 8.6.0 through nvm doesn't help either

stijn 2017-10-20T08:52:22.000041Z

@dominicm would this be a mach or lumo issue? I'm not really sure how to report it if it's lumo though

stijn 2017-10-20T08:52:46.000062Z

As far as I understand it, mach doesn't properly generate the classpath, right?

dominicm 2017-10-20T08:52:46.000131Z

I'm not sure

stijn 2017-10-20T08:53:03.000009Z

it happens on a fresh install of nodejs + mach

stijn 2017-10-20T08:56:02.000003Z

i'll report it first on the mach repo

stijn 2017-10-20T08:58:17.000166Z

for a really simple hello world machfile it works though