This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-05-19
Channels
- # announcements (12)
- # aws (17)
- # babashka (6)
- # beginners (40)
- # cider (14)
- # cljs-dev (14)
- # cljsrn (8)
- # clojure (110)
- # clojure-europe (46)
- # clojure-italy (1)
- # clojure-nl (4)
- # clojure-spec (14)
- # clojure-sweden (3)
- # clojure-uk (29)
- # clojurescript (52)
- # conjure (68)
- # cursive (33)
- # datomic (9)
- # figwheel-main (11)
- # fulcro (97)
- # ghostwheel (1)
- # graalvm (2)
- # helix (53)
- # hoplon (13)
- # joker (6)
- # kaocha (1)
- # leiningen (2)
- # meander (28)
- # mid-cities-meetup (1)
- # observability (1)
- # off-topic (112)
- # pathom (6)
- # pedestal (3)
- # re-frame (16)
- # reagent (16)
- # reitit (2)
- # shadow-cljs (27)
- # spacemacs (2)
- # sql (26)
- # testing (3)
- # utah-clojurians (3)
- # vim (2)
- # xtdb (32)
@dnolen so are you getting around the problem of not knowing where a bundler will output its bundle file by having a convention of having it deployed to output-dir + “main.js” ? I.e. the browser-repl, default-main and index.html all rely on a bundler outputting to main.js
just checking because I’m wresting with this lack of knowledge as well, and if this is going to be the convention going forward, figwheel might as well conform to it
browser-repl
used to look at :output-to
and that was broken in the :bundle
case, so it doesn't anymore
browser-repl
attempts to load main.js
but this is a result of the default index.html
not browser REPL really
default-main
doesn't look for anything by default as you don't need to look for anything for REPLs
but to directly answer your question - nothing in ClojureScript itself needs to know about the bundle output file