This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-11-14
Channels
- # beginners (110)
- # boot (50)
- # cider (29)
- # cljs-dev (80)
- # cljsrn (10)
- # clojure (54)
- # clojure-italy (3)
- # clojure-korea (24)
- # clojure-russia (50)
- # clojure-spec (12)
- # clojure-taiwan (1)
- # clojure-uk (67)
- # clojurebridge (14)
- # clojurescript (118)
- # component (3)
- # cursive (11)
- # datomic (28)
- # dirac (31)
- # emacs (45)
- # flambo (2)
- # hoplon (53)
- # immutant (3)
- # jobs (5)
- # mount (8)
- # off-topic (10)
- # om (5)
- # onyx (52)
- # other-languages (2)
- # parinfer (1)
- # pedestal (1)
- # proton (39)
- # protorepl (2)
- # re-frame (22)
- # remote-jobs (1)
- # ring (13)
- # ring-swagger (2)
- # test-check (9)
- # untangled (28)
- # vim (12)
Just wanted to share a post: how to go from a clean install of ubuntu to re-natal https://gadfly361.github.io/gadfly-blog/2016-11-13-clean-install-of-ubuntu-to-re-natal.html
Can anyone recommend a cljsrn consultant/freelancer? We're cljs and reframe friendly but would love to skip the learning curve on a RN project.
@vikeri a few days late to this, so you might have figured out a fix by now, but I ran into this and got things back to quick compile times by downgrading babel-plugin-transform-es2015-block-scoping
to 6.15.0
these github issues were what pointed me on the way:
https://github.com/babel/babel/issues/4795
https://github.com/facebook/react-native/issues/8475
@nyoung Great, haven’t investigated it more. Hmm, this makes me wonder if we could disable Babel altogether, cljs already outputs fresh ES3 code that don’t need any transpilation...
i haven’t seen any recent comparisons but when annotated correctly, etc., doesn’t closure compiler still output the most optimized results of available options?
An issue would be that the libraries that we use that are written in ES2015 will not be correctly compiled 😞
react packager transpiling libraries)