This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-07-09
Channels
- # announcements (1)
- # aws (4)
- # beginners (55)
- # calva (13)
- # cider (58)
- # clj-kondo (59)
- # cljs-dev (4)
- # clojure (21)
- # clojure-austin (1)
- # clojure-dev (2)
- # clojure-europe (4)
- # clojure-italy (9)
- # clojure-nl (13)
- # clojure-norway (4)
- # clojure-spec (12)
- # clojure-uk (15)
- # clojurescript (22)
- # cursive (11)
- # datomic (3)
- # duct (1)
- # events (1)
- # fulcro (6)
- # graalvm (28)
- # hoplon (9)
- # jobs (2)
- # jobs-discuss (21)
- # mount (14)
- # nrepl (4)
- # off-topic (38)
- # pathom (1)
- # perun (4)
- # re-frame (17)
- # reitit (32)
- # shadow-cljs (44)
- # testing (7)
- # tools-deps (62)
- # vim (10)
I’m working through an issue I’m seeing with simple/advanced compilation and clj->js
. I’ve created a minimal reproducible example here https://github.com/oconn/cljs-sandbox - It seems that $keyword-fn$$
is undefined when parsing keywords in a cljs map.
So looks like it’s because I left :pseudo-names
enabled when I switched to simple
optimizations.
thanks for your help yesterday @dnolen --
fatter resources helped
source-maps vs not source maps was still about a 2x increase on from scratch builds
Also lein
's default JVM parameters were interfering (shakes fist)
(`lein` forces single tier compilation in a misguided attempt to help startup time, at the expense of throughput)
JS is getting weak references where you can give a callback that fires when a specific object is GC'd https://v8.dev/features/weak-references
Should help with coordinating objects/memory between js isolates and other runtimes running in wasm
hey, i'm working on a cljs project with a custom google closure lib (ie, my own js code, specified by the :libs
option), wondering if there's a way to tell figwheel to watch the closure lib's source directory and hotload when i make changes to it
I find debugging ClojureScript to be a lot harder than debugging Clojure. What do I do, for example, with an error message like this? http://ix.io/1O9i Any tips?
For some reason the file I'm currently working in I can't see in the browser. Clicking it in the stacktrace takes me to an empty file.
And even though the stacktrace is a little bit nicer it still does not say exactly on which line the error occurred, or it's off, because the line it points to is (when-not (zero? i)
which is not wrong.
at trainers.cljs:90
at game$trainers$simulate_trainers (trainers.cljs:101)
90 is (when-not ...
and 101 does not exist, or it's just a comment at the end of the file. 😕I found that sometimes I cannot see code in Chrome, but I can in Firefox when I click through stack traces.
I've never seen stack traces show pre-compiled actual code, but can map line numbers if source-maps are available