Hi fellas! Bumped into Uncaught Error: No protocol method IMapEntry.-key defined for type object: (:page-id "notes") Happens when code was generated with release compilation in secretary on some ubuntu linux (14.04 LTS). Same sources compile differently [;)] on macOS High Sierra and don’t cause any trouble after. Versions macOS shadow-cljs 6.4.1 lein 2.8.1 ubuntu shadow-cljs 6.4.1 lein 2.6.1

(:page-id "notes") what is that? that is not valid code?

Yep, this is an artifact after compilation on ubuntu system

check if lein deps :tree is different on the systems

maybe you have something in your ~/.lein/profiles.clj?

thanks! a moment

hmm those don't affect the compiler. there is nothing system dependent in the compiler at all.

does the error appear when compiling with shadow-cljs release your-build --pseudo-names?

I suspect you have an externs issue. they behave very weirdly.

jvms may also be different, I think

shouldn't matter really

it probably is just externs. you can confirm that if the error goes away with --pseudo-names pretty much

yep, trying it

issue persists

hmm at least the error should change?

do you have a full stacktrace?

yup, full stracktrace

app.js?mtime=1545734833000:1642 Uncaught Error: No protocol method IMapEntry.-key defined for type object: (:page-id "notes")
    at $cljs$core$missing_protocol$$ (app.js?mtime=1545734833000:1642)
    at $cljs$core$_key$$ (app.js?mtime=1545734833000:1883)
    at app.js?mtime=1545734833000:10170
    at $cljs$core$seq_reduce$cljs$0core$0IFn$0_invoke$0arity$03$$ (app.js?mtime=1545734833000:3895)
    at $cljs$core$Cons$$.$JSCompiler_prototypeAlias$$.$cljs$core$IReduce$_reduce$arity$3$ (app.js?mtime=1545734833000:4523)
    at $cljs$core$reduce$cljs$0core$0IFn$0_invoke$0arity$03$$ (app.js?mtime=1545734833000:3951)
    at app.js?mtime=1545734833000:10167
    at $cljs$core$array_reduce$cljs$0core$0IFn$0_invoke$0arity$04$$ (app.js?mtime=1545734833000:2864)
    at $cljs$core$IndexedSeq$$.$JSCompiler_prototypeAlias$$.$cljs$core$IReduce$_reduce$arity$2$ (app.js?mtime=1545734833000:3016)
    at $cljs$core$reduce$cljs$0core$0IFn$0_invoke$0arity$02$$ (app.js?mtime=1545734833000:3947)
$cljs$core$missing_protocol$$ @ app.js?mtime=1545734833000:1642
$cljs$core$_key$$ @ app.js?mtime=1545734833000:1883
(anonymous) @ app.js?mtime=1545734833000:10170
$cljs$core$seq_reduce$cljs$0core$0IFn$0_invoke$0arity$03$$ @ app.js?mtime=1545734833000:3895
$JSCompiler_prototypeAlias$$.$cljs$core$IReduce$_reduce$arity$3$ @ app.js?mtime=1545734833000:4523
$cljs$core$reduce$cljs$0core$0IFn$0_invoke$0arity$03$$ @ app.js?mtime=1545734833000:3951
(anonymous) @ app.js?mtime=1545734833000:10167
$cljs$core$array_reduce$cljs$0core$0IFn$0_invoke$0arity$04$$ @ app.js?mtime=1545734833000:2864
$JSCompiler_prototypeAlias$$.$cljs$core$IReduce$_reduce$arity$2$ @ app.js?mtime=1545734833000:3016
$cljs$core$reduce$cljs$0core$0IFn$0_invoke$0arity$02$$ @ app.js?mtime=1545734833000:3947
$cljs$core$merge_with$$.$cljs$core$IFn$_invoke$arity$variadic$ @ app.js?mtime=1545734833000:10165
(anonymous) @ app.js?mtime=1545734833000:17692
$secretary$core$route_matches$$ @ app.js?mtime=1545734833000:17509
(anonymous) @ app.js?mtime=1545734833000:17716
$cljs$core$some$$ @ app.js?mtime=1545734833000:5440
$secretary$core$locate_route$$ @ app.js?mtime=1545734833000:17713
$secretary$core$dispatch_BANG_$$ @ app.js?mtime=1545734833000:17726
$app$routes$on_goog_navigate$$ @ app.js?mtime=1545734833000:17977
$JSCompiler_StaticMethods_fireListeners$$ @ app.js?mtime=1545734833000:17459
$goog$events$EventTarget$$.dispatchEvent @ app.js?mtime=1545734833000:17440
$app$routes$on_window_click$$ @ app.js?mtime=1545734833000:17970

where is the rest?

sorry, updated

hmm. so the only thing I can think of thats actually different between the systems is the cache

try deleting .shadow-cljs/builds

that'll reset the cache

sure! maybe .m2 as well for a good company?

but --pseudo-names didn't use the cache either so it really shouldn't matter

nah .m2 usually doesn't need to be deleted

I assume the issue didn't happen with shadow-cljs compile your-build?

haven’t tried on ubuntu server, will do in few mins

macOS compile and release always produced healthy bundles

I have no idea how the OS could make any difference, never heard of any such issue

Ahem. Dear sir, please accept my resignation as I didn’t had a yarn.lock file in the repo index. Fixed it all.

Found it when I tried to reproduce compile on the remote host.

weird. how does that affect the CLJS code though?

Thank you for guidance and responsiveness! ❤️❤️🍺🍺

I guess cljs might take some decisions based on env

or even different cljs versions?

well, best not to look to close at npm stuff 😉

is there a way to dump npm dep-tree used in compilation? If we’re interested

build reports contain everything that went into the build but besides that there are only the common npm tools

any chance to send you a beer over Patreon or smth?

still need to set that up 😉