This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-09-07
Channels
- # 100-days-of-code (1)
- # announcements (10)
- # aws (2)
- # beginners (134)
- # calva (25)
- # cider (29)
- # cljs-dev (43)
- # clojure (130)
- # clojure-dusseldorf (3)
- # clojure-italy (27)
- # clojure-nl (48)
- # clojure-spec (32)
- # clojure-uk (63)
- # clojurescript (75)
- # core-logic (5)
- # cursive (18)
- # datascript (2)
- # datomic (37)
- # emacs (5)
- # figwheel (13)
- # figwheel-main (55)
- # graphql (1)
- # java (7)
- # jobs (11)
- # jobs-discuss (19)
- # juxt (1)
- # leiningen (16)
- # luminus (10)
- # mount (3)
- # off-topic (40)
- # om (1)
- # onyx (1)
- # pedestal (7)
- # re-frame (40)
- # reagent (81)
- # ring (2)
- # shadow-cljs (32)
- # spacemacs (5)
- # testing (1)
- # tools-deps (48)
For some reason I'm not getting newest cljs source in Chrome's devtools. I know the source has updated, since the console.log fires, but even when I click the logged line, I end up in a line that doesn't have any logging. Is it a problem in the Chrome, or might there be something messing my source maps?
@tomi.hukkalainen_slac are you using the built-in http server or some other web server? the built-in disables all caching to prevent stuff like this, others may not
I’m using the :module-hash-names true
option for my build, looks like manifest.edn
has the mapping to the output name, but how do I make index.html point to that specific js file?
🙂 good question, what should I use?
I want to serve a fulcro app from s3
https://shadow-cljs.github.io/docs/UsersGuide.html#build-hooks would be the answer
or rather would be an answer. there are many things you can do. how are you doing deployment overall?
I’m currently investigating how to go about this, but currently thinking to do shadowcljs release main
with the md5 hashed javascript, push it to S3 and use cloudfront to serve the assets. However, I am trying to get this working with both the index.html
and css
parts of the build
(defn release [server]
(shadow/release :my-build)
(-> (io/file "output-dir" "js" "manifest.edn")
(slurp)
(edn/read-string)
(generate-index-html))
(sh "build-my-css" ...)
(sh "rsync" "-arzt" "path/to/output-dir" server))
@thheller you mean writing the deploy script in clj right?
could be done via make
. Just read the manifest.edn
and generate the index.html
for it via whatever means you prefer?
👍 bit new to this release manually part, thanks!
@thheller any pointers for css bundling?
i was helping someone in another channel with macros and i realized this works:
[2:1]~cljs.user=> (defmacro foo [] `(1 2 3))
#'cljs.user/foo
[2:1]~cljs.user=> (foo)
(1 2 3)
why does it even let me do it? the only reason i’m asking is because i sort of thought it would throw an error
the test for that is if (macroexpand '(foo))
actually works
it doesn’t. the fact that it doesn’t proves that i don’t understand the cljs macro system even a little bit
it's simple, they never work 🙂
that's wise