This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-07-02
Channels
- # aleph (1)
- # architecture (4)
- # beginners (39)
- # boot (12)
- # cider (25)
- # cljs-dev (3)
- # cljsrn (5)
- # clojure (175)
- # clojure-dusseldorf (1)
- # clojure-italy (13)
- # clojure-nl (4)
- # clojure-russia (1)
- # clojure-spec (52)
- # clojure-uk (110)
- # clojurescript (35)
- # data-science (2)
- # datomic (61)
- # editors (8)
- # emacs (2)
- # fulcro (7)
- # graphql (15)
- # hoplon (1)
- # hyperfiddle (3)
- # jobs (4)
- # jobs-discuss (12)
- # juxt (2)
- # lein-figwheel (6)
- # leiningen (35)
- # off-topic (4)
- # onyx (5)
- # parinfer (1)
- # pedestal (63)
- # re-frame (38)
- # reitit (7)
- # ring-swagger (7)
- # rum (2)
- # shadow-cljs (27)
- # tools-deps (10)
- # uncomplicate (16)
@steveb8n Ha! I ran into this issue not so long ago and even submitted a PR https://github.com/thheller/shadow-cljs/pull/333
wold be okay to
FROM urbanslug/shadow-cljs
RUN install aws-cli
In my case I was using it for a CD pipeline@urbanslug cool, thanks. I was using https://hub.docker.com/r/theasp/clojurescript-nodejs but no CLI there either. I’ll make one using yours and will publish on dockerhub as well
@thheller About the first it's possible to have the full JDK installed. About having to have always be installed in the project this would only be done in the project itself during an npm install. Maybe what would work is just a java and npm image then the npm install of the project installs shadow-cljs which would just be a different image anyway.
I'm getting tripped up in the build hooks :shadow.build/mode :release
is being called when I run npx shadow-cljs watch app
@grounded_sage no it isn't?
I’m gonna try to find a Docker image with just node/npm, aws-cli and jdk. if I have any luck I’ll report back
@thheller it is for me for some reason.
{:app {:target :browser
:build-hooks [(util.task/hook) (util.task/css-inline-hook)]...}
(defn css-inline-hook
{:shadow.build/mode :release
:shadow.build/stage :flush}
[build-state & args]
(do
(println "Inlining css")
(css-inline)
build-state))
`ahh ok
{:shadow.build/keys [mode] :as build-state}
and then test it via (when (= mode :dev) ...)
I just saw this in docs and assumed I could filter the hooks that way
The build-state has some important entries which might be useful for your hooks:
:shadow.build/build-id - the id of the current build (eg. :app)
:shadow.build/mode - :dev or :release
I think something like that would be handy. But I recognise that once you add something it's hard to take out 🙂 the example you gave worked fine