This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-05-14
Channels
- # beginners (19)
- # boot (28)
- # cider (1)
- # cljs-dev (12)
- # cljsrn (1)
- # clojure (246)
- # clojure-belgium (4)
- # clojure-berlin (1)
- # clojure-france (4)
- # clojure-italy (7)
- # clojure-russia (11)
- # clojure-serbia (3)
- # clojure-spec (5)
- # clojurescript (106)
- # cursive (4)
- # datomic (7)
- # emacs (1)
- # jobs (6)
- # leiningen (3)
- # luminus (1)
- # lumo (11)
- # off-topic (1)
- # om (7)
- # onyx (1)
- # pedestal (6)
- # re-frame (16)
- # reagent (4)
- # rum (3)
- # spacemacs (1)
- # unrepl (1)
- # untangled (5)
- # vim (1)
> I just wrote a thing for all the node
/ webpack
folks out there, looking for any kind of feedback. https://groups.google.com/forum/?fromgroups=#!topic/clojurescript/AGXku7Ous0Y
@thheller not sure, but this seems to be even more confusing, especially for newcomers :thinking_face:
I mean, it doesn't seem to be useful except an interesting experiment. Maybe you could describe a use case where devs coming from JS would want to use this?
@roman01la well it assumes that you know npm
and then you just get cljs
. no complicated cljs configs, no :externs
. it just works
@roman01la maybe this makes the intent a little clearer
using CLJS in a create-react-app
app: https://github.com/thheller/npm-module-example/tree/master/examples/create-react-app
@thheller like I said, analyzing cljs.core twice isn’t intentional - I can’t offer any insight into why that’s happening right now