Clojurians Log v2

uhg borked something trying to upgrade lumo

with brew?

or Linux?

linux with sudo npm install lumo-cljs -g

https://gist.github.com/selfsame/ab5deb4d3e81aed44a14d5f7efaf0195

don’t use sudo

I guess we didn’t fix that after all?

@selfsame https://github.com/anmonteiro/lumo/issues/234

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

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

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

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

Its not related to the update to 1.7.0. It does it if I do npm install -g lumo-cljs@1.6.0

@mfikes it won’t be faster in Node 9

Node.js disabled snapshots since 8.2.1 or something

https://v8project.blogspot.com/2017/08/about-that-hash-flooding-vulnerability.html

Until Lumo uses the Node 9 codebase ? 🙂

Ahh

@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.

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

@moxaj when you require?

https://github.com/clojure/clojurescript/blob/master/src/main/cljs/cljs/js.cljs#L1052

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

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