This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-05-11
Channels
- # announcements (4)
- # babashka (4)
- # beginners (164)
- # calva (47)
- # cider (1)
- # cljs-dev (29)
- # cljsrn (3)
- # clojure (137)
- # clojure-europe (23)
- # clojure-nl (3)
- # clojure-spec (7)
- # clojure-uk (44)
- # clojurescript (35)
- # component (8)
- # conjure (119)
- # cursive (32)
- # datomic (12)
- # emacs (31)
- # figwheel-main (36)
- # graalvm (10)
- # jobs (2)
- # kaocha (1)
- # lein-figwheel (3)
- # meander (15)
- # mount (3)
- # off-topic (9)
- # pathom (8)
- # quil (4)
- # re-frame (13)
- # reagent (15)
- # remote-jobs (10)
- # shadow-cljs (128)
- # slack-help (2)
- # spacemacs (8)
- # test-check (6)
- # xtdb (6)
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
in general, i'm getting some wierdness... I have been slamming my face against the keyboard for a day
but now the REPL just prints nil
I can't believe how much of a PITA the tooling is to pick up again (after a year off)
long time, no talk
$ 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
shadow-cljs.edn
better yet just remove the core.async dependency completely. shadow-cljs depends on core.async so it will always be available
Fuck yes dude!
btw, I did have to npm i -D ws
you should have shadow-cljs installed in the project itself, that will take care of that also
ok, will do
OMG you have no idea how angry I was getting 😄
thank you sir
I'm curious to know what exactly happened since core.async issues usually fail in different ways 😛
you and me both
:thumbsup: