Fork me on GitHub
#juxt
<
2017-10-20
>
steveb8n07:10:49

@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

dominicm07:10:44

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

steveb8n07:10:17

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

steveb8n07:10:21

fix was the same both times

dominicm07:10:23

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

stijn08:10:50

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

stijn08:10:41

hmmm I'm running node 8.7.0

stijn08:10:04

switching to 8.6.0 through nvm doesn't help either

stijn08:10:22

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

stijn08:10:46

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

dominicm08:10:46

I'm not sure

stijn08:10:03

it happens on a fresh install of nodejs + mach

stijn08:10:02

i'll report it first on the mach repo

stijn08:10:17

for a really simple hello world machfile it works though