This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-02-15
Channels
- # adventofcode (13)
- # aleph (5)
- # announcements (8)
- # beginners (87)
- # calva (9)
- # cider (102)
- # cljs-dev (71)
- # cljsrn (2)
- # clojure (198)
- # clojure-dev (28)
- # clojure-europe (3)
- # clojure-italy (27)
- # clojure-nl (3)
- # clojure-spec (1)
- # clojure-uk (43)
- # clojurescript (121)
- # component (11)
- # cursive (20)
- # data-science (13)
- # datascript (2)
- # datomic (102)
- # dirac (4)
- # duct (5)
- # emacs (14)
- # figwheel-main (7)
- # fulcro (37)
- # hoplon (11)
- # jackdaw (3)
- # jobs (2)
- # leiningen (16)
- # nrepl (2)
- # off-topic (51)
- # pathom (34)
- # pedestal (12)
- # perun (10)
- # portkey (1)
- # re-frame (6)
- # reitit (1)
- # shadow-cljs (21)
- # spacemacs (8)
- # tools-deps (2)
- # vim (2)
I've been getting started with figwheel-main and hit what seems like a bug, but I'm not really sure
In the docs, it shows the default asset-path as "cljs-out/dev" for a dev.cljs.edn file (https://github.com/bhauman/figwheel-main/blob/8ecdaf88831f9acf7b69d2aa0e9897a531146433/docs/docs/compile_config.md#the---print-config-option)
But I'm finding that the default asset-path is /cljs-out/dev
, that is a change from a relative path to an absolute one
There is no difference if you're serving your app off of the root of the host
But if you are serving from a subdirectory (say via nginx)
Then you need to manually specify cljs-out/dev
as the :asset-path
, to ensure that a relative URL is used