This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-03-19
Channels
- # announcements (6)
- # aws (10)
- # beginners (73)
- # bristol-clojurians (2)
- # calva (9)
- # cider (25)
- # clj-kondo (7)
- # clojure (160)
- # clojure-dev (2)
- # clojure-europe (63)
- # clojure-italy (7)
- # clojure-nl (10)
- # clojure-uk (76)
- # clojuredesign-podcast (6)
- # clojurescript (63)
- # cursive (6)
- # data-science (3)
- # datomic (26)
- # duct (59)
- # emacs (1)
- # fulcro (12)
- # graalvm (17)
- # hoplon (23)
- # jobs-discuss (2)
- # kaocha (6)
- # meander (7)
- # off-topic (3)
- # pathom (2)
- # rdf (68)
- # re-frame (12)
- # reagent (20)
- # reitit (5)
- # ring (3)
- # ring-swagger (1)
- # shadow-cljs (14)
- # spacemacs (10)
- # sql (3)
- # tools-deps (30)
- # yada (9)
i'm actually working on migrating a hoplon app from boot => tools.deps and having some success so far
I think he means running within a bootstrapped cljs environment
and no I havent yet attempted that
I would like to, because that could open up a direction for GUI hoplon editors that produce cljs code
currently it relies on a hoplon.cacheKey
java property, which it generates itself (a random UUID) if it's missing
@jjttjj I recommend compiling with shadow and using their bootstrapped support
shadow is a really well built compiler, we have all our apps running on it now
if you get it all working can you send me your shadow config for the bootstrapped project
building a hoplon editor is something I really want to put some time into