This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-12-26
Channels
- # architecture (2)
- # beginners (83)
- # boot (472)
- # cider (10)
- # cljsrn (4)
- # clojure (80)
- # clojure-russia (7)
- # clojure-spec (34)
- # clojure-taiwan (1)
- # clojure-uk (7)
- # clojurescript (19)
- # core-async (5)
- # emacs (7)
- # figwheel (1)
- # hoplon (52)
- # jobs (1)
- # luminus (14)
- # om (1)
- # om-next (3)
- # perun (69)
- # proton (2)
- # protorepl (4)
- # re-frame (28)
- # reagent (6)
- # remote-jobs (1)
@ts1503 Open a second command prompt and type "lein figwheel" to start the Clojurescript compiler. Then reload the page.
thanks @puzzler but figwheel it is development tool. I dont want run him on production server
@ts1503 If the profile doesn't automatically run "lein cljsbuild once name-of-production-profile" before building the uberjar, you may be able to manually run that step to produce the js file, and then hopefully the uberjar will pick it up.
it should be doing that actually, there's a prep task :prep-tasks ["compile" ["cljsbuild" "once" "min"]]
I see the following lines when running lein uberjar
:
Compiling "target/cljsbuild/public/js/app.js" from ["src/cljc" "src/cljs" "env/prod/cljs"]...
Successfully compiled "target/cljsbuild/public/js/app.js" in 14.505 seconds.
this also appears to work correctly in +reagent
and +re-frame
profiles, not sure what's different in the +cljs
one
cljsbuild compile file successfuly. But generated app.js file didnt contain script from core.cljs file