Fork me on GitHub
#shadow-cljs
<
2020-05-11
>
papachan13:05:00

I just included [goog.string :refer [format]] at my require namespaces, in dev it worked fine i can use (format) but it dont find the google lib when i compile a release bundle

papachan14:05:11

anyway i just replace it using (str % " " %) instead of format

papachan14:05:50

Ah didnt know that ! thank you @thheller

thheller17:05:30

when you say eval I assume REPL? which one?

Logan Powell17:05:35

in general, i'm getting some wierdness... I have been slamming my face against the keyboard for a day

Logan Powell17:05:07

but now the REPL just prints nil

Logan Powell17:05:51

I can't believe how much of a PITA the tooling is to pick up again (after a year off)

thheller17:05:11

I don't know what you are doing either so I cannot help unless you tell me more

Logan Powell17:05:31

long time, no talk

thheller17:05:45

$ shadow-cljs browser-repl
shadow-cljs - config: /mnt/c/Users/thheller/code/shadow-cljs/shadow-cljs.edn
shadow-cljs - connected to server
cljs.user=> (defn foo "docstring" [a] a)
#'cljs.user/foo
cljs.user=> (foo 1)
1

Logan Powell17:05:26

shadow-cljs.edn

thheller17:05:29

try [org.clojure/core.async "1.1.587"] but also upgrade shadow-cljs to 2.9.0

thheller17:05:21

better yet just remove the core.async dependency completely. shadow-cljs depends on core.async so it will always be available

thheller17:05:29

and that way you get the version it expects

Logan Powell18:05:41

Fuck yes dude!

Logan Powell18:05:01

btw, I did have to npm i -D ws

thheller18:05:38

you should have shadow-cljs installed in the project itself, that will take care of that also

Logan Powell18:05:01

OMG you have no idea how angry I was getting 😄

thheller18:05:50

I'm curious to know what exactly happened since core.async issues usually fail in different ways 😛

Logan Powell18:05:05

you and me both