Clojurians
#lumo
<
2017-08-18
>

This page is not created by, affiliated with, or supported by Slack Technologies, Inc.

selfsame00:08:19

uhg borked something trying to upgrade lumo

selfsame00:08:57

linux with sudo npm install lumo-cljs -g

anmonteiro00:08:54

don’t use sudo

anmonteiro00:08:00

I guess we didn’t fix that after all?

selfsame00:08:16

think i have to use sudo to do any -g npm install

selfsame00:08:32

ah nice there's binaries i can use in the meantime

rberger00:08:42

I’m having the same problem when trying to install on docker with a debian based image I’m not explicitly using sudo, but it runs as root

mfikes00:08:29

Nice. For this operation, Lumo appears to be faster than Node itself.

$ time lumo -e '(+ 2 3)'
5

real	0m0.374s
user	0m0.332s
sys	0m0.066s
$ time node -e 'console.log(2+3)'
5

real	0m0.493s
user	0m0.444s
sys	0m0.028s

rberger00:08:44

Its not related to the update to 1.7.0. It does it if I do npm install -g [email protected]

anmonteiro00:08:08

@mfikes it won’t be faster in Node 9

anmonteiro00:08:30

Node.js disabled snapshots since 8.2.1 or something

mfikes00:08:33

Until Lumo uses the Node 9 codebase ? :slightly_smiling_face:

dominicm07:08:56

@anmonteiro I think Macs might configure differently by default. Linux boxes require root access to do global installs. Or at least, all the ones I've seen do.

moxaj22:08:51

@anmonteiro with the verbose flag set, lumo dumps some compiled namespaces to the stdout, is that expected?

anmonteiro22:08:08

@moxaj when you require?

anmonteiro22:08:28

^ if this is what you’re seeing, then expected

moxaj22:08:34

I see. Really clutters the output, but managable I guess