Have you folks ever encountered the problem in https://github.com/anmonteiro/lumo/issues/308. Can anyone reproduce it?
@richiardiandrea I have seen similar error message, each time a different namespace
Have’t been able to diagnose the root cause
And when I touch some cljs and ClojureScript recompiles, it’s gone. Seems like a startup thing or maybe some concurrency thing
Having said that, I use :parallel-build true
I realize now
:parallel-build
has no effect in Lumo
yeah I don't have parallel build on but this looks like some issue with asynchronicity...haven't had time to dig though
I think that the function js/setTimeout is not found when building lumo in dev build.
$ 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?