While compiling some code today using lumo against master Clojurescript today I have run against the following:

this.mseq.cljs$core$ISeq$_first$arity$1(...).cljs$core$IMapEntry$_key$arity$1 is not a function
cljs.core.KeySeq.cljs$core$ISeq$_first$arity$1 (NO_SOURCE_FILE <embedded>:1640:411)
Object.cljs.core.first (NO_SOURCE_FILE <embedded>:507:165)
Function.cljs.core.seq_reduce.cljs$core$IFn$_invoke$arity$3 (NO_SOURCE_FILE <embedded>:660:115)
cljs.core.KeySeq.cljs$core$IReduce$_reduce$arity$3 (NO_SOURCE_FILE <embedded>:1640:248)
Function.cljs.core.reduce.cljs$core$IFn$_invoke$arity$3 (NO_SOURCE_FILE <embedded>:667:181)
(Object.lumo$cljs-deps$dependency-order)
(lumo/closure:4537:270)
(lumo/closure:4544:3)
(lumo/closure:4550:3)
Function.lumo.closure.build.cljs$core$IFn$_invoke$arity$3 (lumo/closure:4556:3)

@juhoteperi awesome! Will get to those today

@richiardiandrea I thought Mike Fikes addressed that, but maybe there’s a missing case

@richiardiandrea my guess it's the PHM with nil entry. I'm double checking now

I can see now that is the case. I'll open up a ticket with a patch. I also did not update the PHM iterator to support that nil case either 😞

Awesome cool folks i.did not know what that meant but I thought I should report it 😸 @tmulvaney you can send the patch over if you want me to try the fix ;)

It's attached here https://dev.clojure.org/jira/browse/CLJS-2496

hopefully that works @richiardiandrea

@tmulvaney will check thanks!!

This main support stuff is actually pretty neato

getting it setup was a little bit fiddly but the fact that we have a generic way to point any REPL at build and run something is pretty cool

@juhoteperi 2375 needs a rebase on master

oh never mind, one sec

was just missing --keep-cr

@dnolen by any REPL you mean also planck and lumo, wink wink nudge nudge 😄

@juhoteperi ok 2389 does appear to need a rebase

@richiardiandrea heh no, not bootstrapped stuff

but that’s not that challenging anyway

I mean this isn’t even really a problem there

not that this is going to extended for that case

yep true that

lumo always tries to follow anyways, so we'll adapt so that we can reuse the documentation 😄

but anyways being able to point at build and load up some abritrary script before running something, or eval some arbitrary expression before seems useful for testing

I like where this is going

@juhoteperi I’m going to stop on applying the others until 2389 gets fixed up, if I don’t get to this today will definitely do it some point this weekend

I think this + global caching of JAR deps would be a very nice release

as usual there’s tons of other stuff too

@dnolen if you have some lil' time for CLJS-2492 and CLJS-2493 let me know...i would love to support source maps cleanly in lumo

@richiardiandrea yes I’ll look at those, unlikely to cut a release this week or next anyway but soon after I hope

thanks a lot

stuff like this works now

java -cp cljs.jar:src clojure.main -m cljs.repl.node -o out -e "(+ 3 4)" -m foo.core 1 2

outputs

ClojureScript Node.js REPL server listening on 53734
7
Analyzing file:/Users/davidnolen/development/clojure/main-cljs/src/foo/core.cljs
args: (1 2)
*command-line-args* (1 2)

we could probably supply our own main to clean this up I think?

@dnolen if I understand correctly, in lumo we execute *main-cli-fn*...when it has been def-ed we run that:

(defn- ^:export run-main-cli-fn
  []
  (when (fn? *main-cli-fn*)
    (apply *main-cli-fn* *command-line-args*)))

@richiardiandrea this has nothing to do with Lumo. David is talking about Java main classes

not portable to Lumo either

oh sorry, yeah I was afraid I did not get something, too many mains 😄

@dnolen https://dev.clojure.org/jira/secure/attachment/17699/CLJS-2389-7.patch rebased

@tmulvaney @dnolen CLJS-2496 seems to work fine here, I don't receive that error in lumo anymore