lumo

:lumo: Standalone ClojureScript environment. Currently at version 1.9.0
2017-07-15T16:11:37.334563Z

I was running sudo npm install lumo-cljs -g and hit

Error: EACCES: permission denied, open 'lumo_linux64.zip'
sh: nodejs: command not found
workes with
su
# npm install lumo-cljs -g
just thinking out loud...

anmonteiro 2017-07-15T16:38:08.480480Z

@hlolli see the latest open issue in Lumo

anmonteiro 2017-07-15T16:38:26.482147Z

We could probably support that, but I haven't investigated

anmonteiro 2017-07-15T16:38:32.482675Z

PR welcome if you wanna dig

2017-07-15T16:45:56.522166Z

yes, I think the script needs to detect if the active user is super user and do whatever action is there with sudo.

pesterhazy 2017-07-15T17:03:28.618313Z

@hlolli not sure - if a process runs as sudo, its children are also run as root

pesterhazy 2017-07-15T17:04:51.625170Z

the whole "npm as root" vs "npm as normal user" situation is a mess

pesterhazy 2017-07-15T17:05:02.626155Z

it trips people up all the time

2017-07-15T17:06:50.635633Z

The upstream npm_install.js is not on the github repo?

2017-07-15T17:09:24.648948Z

haha, I'm blind 🙂

2017-07-15T17:10:07.653022Z

https://github.com/anmonteiro/lumo/tree/master/scripts still dont see it here, wtf

2017-07-15T17:10:26.654629Z

noo first packages

pesterhazy 2017-07-15T17:10:26.654658Z

compare the paths

1👀
2017-07-15T17:10:30.654976Z

ok

anmonteiro 2017-07-15T17:19:27.702771Z

@pesterhazy @hlolli I’ll be eternally grateful if you wanna figure this out

1👀
2017-07-15T19:06:44.268478Z

solved this sudo npm install lumo-cljs -g --unsafe-perm works from the documentation

If npm was invoked with root privileges, then it will change the uid to the user account or uid specified by the user config, which defaults to nobody. Set the unsafe-perm flag to run scripts with root privileges.
this can be added
"config": {
    "unsafe-perm":true
}

2017-07-15T19:07:07.270224Z

PR, 5 mins

anmonteiro 2017-07-15T19:07:36.272518Z

👍

anmonteiro 2017-07-15T19:07:46.273487Z

@hlolli you can try it with sudo npm install .

anmonteiro 2017-07-15T19:07:50.273873Z

if you cd packages/lumo

2017-07-15T19:08:39.277860Z

that's what I did, there I got an error which led me to the answer the error was

cannot run in wd

2017-07-15T19:09:22.281377Z

which led me to this answer, but this is in no way a descriptive error message

2017-07-15T20:17:32.625946Z

someone got instaparse running in lumo, I'm getting

ERROR in file instaparse/gll.cljc
	 (new)
	 Function.cljs.core.ex_info.cljs$core$IFn$_invoke$arity$3 (NO_SOURCE_FILE <embedded>:1935:200)
	 Function.cljs.analyzer.error.cljs$core$IFn$_invoke$arity$3 (NO_SOURCE_FILE <embedded>:2482:92)
	 (NO_SOURCE_FILE <embedded>:5947:100)
	 z (NO_SOURCE_FILE <embedded>:5948:13)
	 (NO_SOURCE_FILE <embedded>:5942:232)
	 (NO_SOURCE_FILE <embedded>:5862:482)
	 Object.cljs.js.load_macros (NO_SOURCE_FILE <embedded>:5838:464)
	 (NO_SOURCE_FILE <embedded>:5857:20)
	 Object.cljs.js.load_macros (NO_SOURCE_FILE <embedded>:5838:464)

2017-07-15T20:48:32.771394Z

https://clojars.org/com.lucasbradstreet/instaparse-cljs works, I file a ticket anyway, they are doing something wrong if they are claiming cljs compatability on instaparse (not -cljs).

futuro 2017-07-15T21:03:55.843207Z

Anyone have suggestions on debugging cljs code in lumo?

futuro 2017-07-15T21:04:43.847160Z

I've got a weird issue with some protocols that I'm trying to sort out