This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-01-29
Channels
- # aws (1)
- # aws-lambda (1)
- # beginners (34)
- # boot (61)
- # cljs-dev (126)
- # cljsjs (10)
- # cljsrn (4)
- # clojure (27)
- # clojure-russia (7)
- # clojure-spec (1)
- # clojure-uk (26)
- # clojurescript (42)
- # cursive (31)
- # datascript (4)
- # datomic (16)
- # hoplon (51)
- # klipse (1)
- # lein-figwheel (1)
- # lumo (79)
- # off-topic (16)
- # om (7)
- # parinfer (5)
- # planck (2)
- # re-frame (6)
- # reagent (3)
- # ring-swagger (5)
- # untangled (11)
Ah… when classnames.inc.js is loaded, it doesn’t define window.classNames. Instead it defines module.exports.
@juhoteperi: with the new closure compiler what does this mean for our existing cljsjs packages, how do we upgrade?
@flyboarder: I don't think there will be a one-size-fits-all type solution. Currently thinking that maybe we investigate how to package react and maybe 1-2 other popular ones and provide these with a -closure modifier
@flyboarder: still lots to figure out (for me at least)
Yeah I just want to make sure I'm going in the right direction
I think old approach is still valid for now. Will take a couple of weeks until someone figured out the consequences of all the new stuff
I think old approach is still valid for now. Will take a couple of weeks until someone figured out the consequences of all the new stuff
I want to package react-google-login, is there a sort of "absolute beginners guide to cljsjs packaging" that I could reference?
Should I make cljsjs packages for all npm dependencies of the lib I'm re-packaging?