This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-04-29
Channels
- # announcements (4)
- # architecture (1)
- # beginners (113)
- # boot (17)
- # calva (40)
- # cider (9)
- # clara (1)
- # cljs-dev (21)
- # cljsrn (21)
- # clojure (47)
- # clojure-dev (8)
- # clojure-europe (2)
- # clojure-italy (46)
- # clojure-nl (10)
- # clojure-spec (1)
- # clojure-turkiye (1)
- # clojure-uk (46)
- # clojurescript (102)
- # core-async (21)
- # cursive (35)
- # data-science (1)
- # datomic (7)
- # emacs (2)
- # graphql (1)
- # lumo (15)
- # nrepl (4)
- # nyc (1)
- # off-topic (5)
- # overtone (3)
- # pathom (10)
- # quil (6)
- # re-frame (30)
- # reagent (7)
- # reitit (33)
- # rewrite-clj (1)
- # shadow-cljs (37)
- # spacemacs (73)
- # test-check (3)
- # testing (2)
- # vim (59)
Yeah, you can just throw the artifact on a CDN for prod. For hosting the code on js infrastructure like npm, Mori took the approach of just the advanced compiled artifact on npm, while datascript took the approach of having the npm installer download lein and run that lein stuff for you (iirc). But neither approach is perfect, since goog closure doesn't integrate perfectly with the npm ecosystem.
There is something simple as clj -A:docs
>> connect localhost:3214
and see the docs of current project?
@souenzzo Should be relatively easy to write a Clojure function that would do that based on one of the various doc-generator libraries...
@souenzzo https://github.com/weavejester/codox is somewhat popular