This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-08-04
Channels
- # arachne (1)
- # beginners (41)
- # boot (92)
- # capetown (8)
- # cider (10)
- # cljsjs (4)
- # cljsrn (42)
- # clojure (94)
- # clojure-india (1)
- # clojure-russia (48)
- # clojure-sanfrancisco (1)
- # clojure-spec (34)
- # clojure-uk (13)
- # clojurescript (29)
- # cursive (12)
- # datavis (4)
- # datomic (10)
- # dirac (63)
- # editors-rus (16)
- # emacs (57)
- # funcool (5)
- # hoplon (22)
- # jobs (2)
- # lein-figwheel (3)
- # leiningen (5)
- # onyx (51)
- # other-languages (2)
- # proton (1)
- # protorepl (2)
- # re-frame (34)
- # remote-jobs (1)
- # sfcljs (5)
- # spacemacs (1)
- # specter (2)
- # sql (20)
- # test-check (54)
- # yada (1)
folks, for a package which has both a 'full distribution' js/css (where dependencies are linked in) and a 'bare' dist without linked dependencies, should I do anything with the bare .js/.css files? I can't really put them into development or production, should I just not bother sifting them from the dist zip?
^ just updated that PR to include autogenerated externs file
Trying to upgrade https://github.com/cljsjs/packages/tree/master/react-datepicker - the latest versions don't have a dist dir, so have to manually run builds with npm install. I see there are some examples of that (radium), so that's probably okay? But then I run the grunt build task and it requires a ruby gem... Is it fine to run "gem install scss_lint" as well?