Clojurians
#lumo
<
2017-03-23
>

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

mozinator11:03:38

anyone tried running lumo in react-native ?

otfrom13:03:41

does lumo work with node 7.7.3? (I'm running ubuntu 16.10)

otfrom13:03:48

[email protected]:~$ sudo npm install -g  lumo-cljs
[sudo] password for bld: 
/usr/bin/lumo -> /usr/lib/node_modules/lumo-cljs/bin/lumo

> [email protected] install /usr/lib/node_modules/lumo-cljs
> node scripts/npm_install.js


 Downloading [============================------------] :rate/bps 70% 13.0s
Download failed.
npm ERR! Linux 4.8.0-43-generic
npm ERR! argv "/usr/bin/nodejs" "/usr/bin/npm" "install" "-g" "lumo-cljs"
npm ERR! node v7.7.3
npm ERR! npm  v4.1.2
npm ERR! code ELIFECYCLE

npm ERR! [email protected] install: `node scripts/npm_install.js`
npm ERR! Exit status 255
npm ERR! 
npm ERR! Failed at the [email protected] install script 'node scripts/npm_install.js'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the lumo-cljs package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node scripts/npm_install.js
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs lumo-cljs
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls lumo-cljs
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /home/bld/npm-debug.log

otfrom13:03:33

the npm-debug.log isn't giving me a lot go go on either

dominicm13:03:33

Looks the same as from the other day :thinking_face:

otfrom13:03:52

dominicm well, if you are going to follow me from forum to forum. :wink:

otfrom13:03:13

talked about it in #juxt here

dominicm13:03:16

I'm in all slack channels :smile:

mozinator13:03:25

anyone got lumo running on react-native ?

otfrom13:03:30

dominicm that looks very familiar, but I'm not hit023

otfrom13:03:17

looks like I'm just supposed to keep hitting it. Is this common in nodejs things?

dominicm13:03:29

@otfrom If you've run it a few times & still not worked, no.

dominicm13:03:47

Not common in nodejs. I think that Lumo's dependency nexe is a bit involved, so a bit pita.

otfrom13:03:55

dominicm only like 4-5 times. :stuck_out_tongue:

hit02313:03:02

I try to run it every morning after waking up. Doesn't seem to be working

otfrom13:03:22

omg it just worked

otfrom13:03:27

give it a try now hit023

otfrom13:03:30

[email protected]:~$ sudo npm install -g  lumo-cljs
/usr/bin/lumo -> /usr/lib/node_modules/lumo-cljs/bin/lumo

> [email protected] install /usr/lib/node_modules/lumo-cljs
> node scripts/npm_install.js


 Downloading [========================================] :rate/bps 100% 0.0s

/usr/lib
└── [email protected] 

[email protected]:~$ lumo 
/usr/local/bin/lumo: line 1: /lumo.exe: No such file or directory

otfrom13:03:14

and mach is allegedly installed now too

otfrom13:03:17

[email protected]:~$ sudo npm install -g mach
/usr/lib
└─┬ [email protected] 
  ├── [email protected] 
  ├─┬ [email protected] 
  │ └── [email protected] 
  ├── [email protected] 
  ├── [email protected] 
  ├── [email protected] 
  ├── [email protected] 
  ├── [email protected] 
  └── [email protected] 

[email protected]:~$ mach 
/usr/local/bin/lumo: line 1: /lumo.exe: No such file or directory

otfrom13:03:25

tho not in a usable way

hit02314:03:17

still the same error @otfrom

otfrom14:03:38

well, even if you got past that it might not work

dominicm14:03:27

Works on best linux (arch)

otfrom14:03:14

I'm on ubuntu 16.10, so I shouldn't be too far off

otfrom14:03:19

what version of node are you using?

dominicm14:03:14

npm --version is 4.1.2

otfrom14:03:48

[email protected]:~$ npm --version
4.1.2
[email protected]:~$ node --version
v7.7.3

otfrom14:03:26

so I'm 0.0.1 versions behind you on node

mozinator14:03:41

many kudus to the whole lumo team !

mozinator14:03:00

no more JVM makes me very happy !

otfrom14:03:40

I'm sure people not used to the jvm find that just as frustrating as I'm finding node atm

dominicm14:03:06

@otfrom yanno what

anmonteiro14:03:09

The NPM installation is a bit flaky and I have no idea why

anmonteiro14:03:19

@mozinator thanks. What do you mean by running Lumo in React Native?

otfrom14:03:54

that works

mozinator14:03:54

to embed lumo into an react-native based app

otfrom14:03:22

I had to sudo rm -fr /usr/local/lib/node_modules/lumo-cljs and sudo rm /usr/local/bin/lumo

anmonteiro14:03:41

Hrm. Can you embed Node in a React Native app?

otfrom14:03:46

but after doing those and having that lumo from the .zip in ~/bin which is in my $PATH things seem happy

otfrom14:03:58

dominicm should I do the same with mach?

mozinator14:03:34

@anmonteiro good question, will check

anmonteiro14:03:37

Lumo is basically the Node executable with a custom init script for CLJS + dark magic to make it start ultra fast

anmonteiro14:03:58

If you can embed Node in a React Native app, you should be able to embed Lumo

dominicm14:03:29

@otfrom mach doesn't really need lumo.

anmonteiro14:03:35

But it might not be starightforward at all

dominicm14:03:56

@otfrom as in, it shouldn't need to install it as a dependency. Don't know how to do exclusions.

anmonteiro14:03:03

And you may need to compile Lumo for ARM, which I still haven't been able to

dominicm14:03:30

@anmonteiro lack of resources? Or technical issues?

anmonteiro14:03:43

If anyone's a big RaspberryPi fan, pls get in touch

anmonteiro14:03:17

@dominicm mostly lack of time to go through the pain of figuring every little thing out

dominicm14:03:48

It also built on arm

anmonteiro14:03:02

I tried to cross compile and it succeeded, but then failed to launch on rPi because it's dynamically linked to stdlibc

dominicm14:03:08

ah, not sure about that.

anmonteiro14:03:17

So I must have been doing something wrong

anmonteiro14:03:43

@dominicm right, I know it's possible. Just my time has been limited these days

dominicm14:03:04

No, just figured it was hardware. Wanted to show it built. :stuck_out_tongue:

whitecoop14:03:31

@dominicm @anmonteiro I'd love to see lumo on the rPi, but when I started digging into compiling for ARM it was all new and therefore slow going and I'm up against the time issue too. :smile: Last @anmonteiro and I chatted, he recommended looking into using nodejs' make. And that's where I left it

richiardiandrea15:03:49

Maybe an FAQ, but is it possible to pass options to node's command line?

dominicm15:03:54

@richiardiandrea:

(def v8 (js/require "v8")) (.setFlagsFromString v8 "--nouse_strict")

richiardiandrea15:03:08

Awesome thanks, I am going to need to increment the memory size

richiardiandrea18:03:03

are symlinks (as in yarn link) picked up in lumo? Probably they should as it is node stuff at the end of the day

dominicm18:03:13

They should be.

dominicm18:03:32

Resolution of those shouldn't be different.

richiardiandrea18:03:27

weird I get always the behavior of the old package, not the package I am testing with link

dominicm18:03:53

Is the old one in your node modules folder?

richiardiandrea18:03:53

but the file in node_modules points to the correct one

dominicm18:03:44

That doesn't make sense to me: how could it still find the old one :thinking_face:

richiardiandrea18:03:11

yeah doesn't make sense to me either, will investigate more

dominicm18:03:52

Look for global node module folders, try compare to plain node too.

richiardiandrea18:03:48

yes plain node is my next step

dominicm18:03:50

Lumo does slightly different resolution afaik, particularly when run via #!

richiardiandrea18:03:07

oh that might be then, I am using it in a script

dominicm18:03:53

I reported this a little while ago, @anmonteiro said something about having to manually implement it.

dominicm18:03:18

Might be worth you looking at how mach works around it

richiardiandrea18:03:31

ok cool will do it

richiardiandrea18:03:48

thanks @dominicm

anmonteiro18:03:44

@dominicm I did implement it, it’s in 1.2.0 :slightly_smiling_face:

dominicm18:03:38

@anmonteiro ooh. I'll have to try my examples again.

richiardiandrea19:03:14

:facepalm: for me, everything is good guys, sorry for the noise, resolution works

dominicm19:03:40

Aha :laughing: at least I now know I can fix mach

richiardiandrea19:03:07

ah ah true, let's look at the bright side :smile:

richiardiandrea19:03:36

lumo is becoming an indispensable tool for me (and my colleagues), thanks @anmonteiro !

anmonteiro19:03:34

that is awesome

anmonteiro19:03:39

I wish I had more time to work on it

anmonteiro19:03:53

I wonder how a Patreon campaign would go

richiardiandrea19:03:03

uhm I would pitch in :wink:

anmonteiro19:03:03

or whatever people use to get funded to work on open source

richiardiandrea19:03:43

especially for improving completion, we have compiler + sexp and we can get pretty fancy :smile: I read vscode does expression evaluation (getting rid of loops, side effects and deep recursion) for completing the objects in the editor

dominicm19:03:49

For the JUXT training course next week we're using mach/lumo to build the presentation

dominicm19:03:37

It's a real confluence of technology: lumo powering mach. In the presentation we use Klipse. And it's all compiled from adoc (which I eventually want to do via lumo)

dominicm19:03:59

We'll open source the presentation building stuff soon. Working with @viebel to make it super friendly to klipse.

anmonteiro19:03:40

@dominicm w-o-w

anmonteiro19:03:42

that is awesome

richiardiandrea19:03:20

another interesting thing is process.argv in lumo does not trim nexe stuff...but I guess it is unavoidable

richiardiandrea19:03:40

so what is the suggested way to pass arguments to a script?

anmonteiro19:03:51

@richiardiandrea hrm, you mean Lumo args?

anmonteiro19:03:09

they should be in lumo.core/*command-line-args*, no?

richiardiandrea19:03:27

ah, did not know that :blush:

anmonteiro19:03:15

so one other thing I wanna work on is the lumo website

anmonteiro19:03:21

write a bunch of docs

richiardiandrea19:03:45

ah ah yes that is always good to do :smile:

anmonteiro19:03:24

I wonder if I opened an Open Collective thing https://opencollective.com/

anmonteiro19:03:45

if people would back Lumo and help me take some time to build stuff for it

anmonteiro19:03:05

probably too early for that

richiardiandrea19:03:01

I think it is a good idea, why do you think it is early?

anmonteiro19:03:35

@richiardiandrea I don’t think many people would back it, simply because it’s not evolved enough to be prolific (yet?)

dominicm20:03:44

@anmonteiro you might find private companies are a good backer

dominicm20:03:01

@anmonteiro I can highly suggest you write your docs in asciidoctor. If nothing else because it has a table of contents! The best part is that it can include real code from files, so you can include parts of code from a test suite or output from real commands and such.

dominicm20:03:28

There's a module that takes screenshots of websites during build.

dominicm20:03:08

That's probably not the best bit. But it's exciting

anmonteiro20:03:38

@dominicm hrm, maybe, thanks for suggesting that. I wonder if there would be companies interested in backing Lumo though, given it’s only 4 months old :slightly_smiling_face: