lumo

:lumo: Standalone ClojureScript environment. Currently at version 1.9.0
richiardiandrea 2017-11-14T03:43:13.000001Z

Have you folks ever encountered the problem in https://github.com/anmonteiro/lumo/issues/308. Can anyone reproduce it?

borkdude 2017-11-14T09:47:23.000153Z

@richiardiandrea I have seen similar error message, each time a different namespace

borkdude 2017-11-14T09:48:50.000344Z

Have’t been able to diagnose the root cause

borkdude 2017-11-14T09:49:20.000193Z

And when I touch some cljs and ClojureScript recompiles, it’s gone. Seems like a startup thing or maybe some concurrency thing

borkdude 2017-11-14T09:50:08.000396Z

Having said that, I use :parallel-build true I realize now

anmonteiro 2017-11-14T17:19:05.000209Z

:parallel-build has no effect in Lumo

richiardiandrea 2017-11-14T17:53:32.000458Z

yeah I don't have parallel build on but this looks like some issue with asynchronicity...haven't had time to dig though

2017-11-14T23:26:00.000189Z

I think that the function js/setTimeout is not found when building lumo in dev build.

2017-11-14T23:32:32.000222Z

$ node target/bundle.js -c target
Lumo 1.8.0-beta
ClojureScript 1.9.946
Node.js v8.5.0
 Docs: (doc function-name-here)
       (find-doc "part-of-name-here")
 Source: (source function-name-here)
 Exit: Control+D or :cljs/quit or exit

cljs.user=> js/setTimeout
setTimeout is not defined
	 (evalmachine.<anonymous>:1:1)
	 ContextifyScript.Script.runInContext (vm.cljs:53:29)
	 Object.runInContext (vm.cljs:108:6)
	 (Object.lumoEval)
	 (Object.lumo.repl.caching_node_eval)
	 (evalmachine.<anonymous>:5837:273)
	 E (evalmachine.<anonymous>:5838:269)
	 Object.cljs.js.eval_str_STAR_ (evalmachine.<anonymous>:5839:373)
	 Function.cljs.js.eval_str.cljs$core$IFn$_invoke$arity$5 (evalmachine.<anonymous>:5842:508)
	 Object.lumo.repl.execute_text (evalmachine.<anonymous>:6619:475)
from the lumo binary
cljs.user=> js/setTimeout
#object[setTimeout]
ideas @anmonteiro?