This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-05-03
Channels
- # aws-lambda (6)
- # beginners (38)
- # boot (39)
- # cider (44)
- # cljs-dev (9)
- # cljsrn (96)
- # clojure (142)
- # clojure-dev (6)
- # clojure-dusseldorf (8)
- # clojure-greece (45)
- # clojure-ireland (3)
- # clojure-italy (7)
- # clojure-norway (6)
- # clojure-russia (26)
- # clojure-sg (16)
- # clojure-spec (31)
- # clojure-uk (39)
- # clojurescript (125)
- # cursive (38)
- # datascript (4)
- # datomic (18)
- # emacs (34)
- # figwheel (2)
- # hoplon (3)
- # immutant (23)
- # jobs (1)
- # lambdaisland (2)
- # lumo (13)
- # off-topic (77)
- # om (8)
- # onyx (9)
- # pedestal (2)
- # play-clj (1)
- # re-frame (52)
- # reagent (3)
- # rum (4)
- # spacemacs (2)
- # specter (4)
- # unrepl (37)
- # untangled (8)
- # vim (79)
- # yada (1)
Thought I might write here, maybe obvious things: when in a source map I replace sources
from [core.cljs]
to [../src/core.cljs]
Chrome DevTools is happy again
Even in older versions of node.js like 6.10 (no problem detected in > 7.6)
so what was the problem? why ../src/core.cljs
works? src should not be exposed to dev server, this sounds to me like a misconfiguration on your part and that made it work just by coincidence
from your last post, the take away was that the whole issue was on node.js side, cljs generated correct source maps, but old node.js did something wrong
Yes it was on the node.js side, it looks like the embedded node-inspector
at some point and made some mess around it 😀
This looks interesting https://prepack.io/
FYI, prepack just hit HN: https://news.ycombinator.com/item?id=14257744
So I did some testing with basic web app. Prepack does a great job at folding computations. The output size is almost the same as Closure would produce, but the code is running two times faster https://twitter.com/roman01la/status/859849179149021184