This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-10-19
Channels
- # 100-days-of-code (5)
- # announcements (1)
- # aws (1)
- # beginners (112)
- # cider (135)
- # cljdoc (6)
- # clojure (111)
- # clojure-dev (8)
- # clojure-italy (3)
- # clojure-nl (5)
- # clojure-sweden (3)
- # clojure-uk (152)
- # clojurescript (101)
- # datascript (14)
- # datomic (61)
- # editors (1)
- # emacs (29)
- # events (7)
- # figwheel (3)
- # figwheel-main (15)
- # fulcro (18)
- # funcool (2)
- # graphql (1)
- # juxt (2)
- # off-topic (51)
- # om (1)
- # overtone (28)
- # perun (2)
- # reagent (1)
- # reitit (6)
- # ring-swagger (5)
- # shadow-cljs (112)
- # spacemacs (49)
- # tools-deps (10)
- # unrepl (11)
- # yada (10)
FWIW, on the AOT / clj
question, I realized I could just add classes
to :paths
and call (compile 'my.ns)
as part of application startup...
For dev, I just put it in src/user.clj
🙂
For production, yes, we build an uberjar and deploy just that. That particular library is up on Clojars right now so boot
takes care of the AOT. I am still considering how best to handle it either as a direct dependency (locally) or AOT'd and packaged for Clojars via clj
and some tooling.
Taking small steps toward solving the exceedingly few AOT needs we have 🙂