This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-09-02
Channels
- # announcements (3)
- # aws (3)
- # bangalore-clj (1)
- # beginners (88)
- # boot (7)
- # braveandtrue (10)
- # cider (6)
- # cljdoc (8)
- # cljsrn (3)
- # clojure (33)
- # clojure-germany (2)
- # clojure-italy (1)
- # clojure-spec (44)
- # clojure-uk (8)
- # clojurescript (14)
- # datomic (5)
- # emacs (6)
- # events (1)
- # figwheel-main (8)
- # fulcro (9)
- # leiningen (11)
- # lumo (3)
- # off-topic (119)
- # parinfer (2)
- # pedestal (1)
- # re-frame (11)
- # reagent (12)
- # shadow-cljs (162)
- # unrepl (4)
does anyone have two separate SPAs in a single app?
I mean I didn't want to do all the routing in Clojurescript, and maybe the other page I'm writing doesn't really shared much JS code with the main page
doesn't seem so easy though since the js is all compiled in a single app.js
I’ve done client/server/ssr-layer as three different compilation targets (different subfolders under src). I’m not sure whether that is better or worse than entirely separate configs, but it basically comes down to which folders you tell the compiler to slurp source files from.
@ai20 ive got 3 SPAs running on http://bruh.io simultaneously but they’re compiled and downloaded separately
ah nice @samueldev the code is not available by any chance?
and ok if I just have to make different compilation targets it should not be too hard
I guess the different compilation targets can also share code anyway
Closure will still kill all the unnecessary stuff anyway from each of the targets right @henrik?
@andrea.crotti Yes, although for the SSR build, the target was Node, so conditions apply WRT Closure Compiler. For browser, sure.