This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-09-15
Channels
- # aleph (14)
- # aws (5)
- # beginners (144)
- # bitcoin (1)
- # boot (14)
- # chestnut (13)
- # cljs-dev (58)
- # cljs-experience (1)
- # cljsrn (47)
- # clojure (107)
- # clojure-dev (9)
- # clojure-finland (12)
- # clojure-gamedev (4)
- # clojure-russia (2)
- # clojure-sanfrancisco (1)
- # clojure-spec (5)
- # clojure-uk (28)
- # clojurescript (34)
- # cursive (9)
- # datomic (3)
- # emacs (11)
- # garden (16)
- # graphql (9)
- # hoplon (3)
- # jobs (2)
- # juxt (6)
- # off-topic (32)
- # om (10)
- # onyx (1)
- # pedestal (4)
- # proton (1)
- # re-frame (14)
- # reagent (8)
- # ring (1)
- # ring-swagger (34)
- # shadow-cljs (19)
- # sioux-falls (1)
- # spacemacs (16)
- # testing (14)
Sorry about that, I can read english but bad at speak 😛
So I always inclined to speak Chinese ...
sometimes I think writing that file is boring too, although mostly I just copy from my minimal-xyz
projects
I found debugging macros is convenient with Lumo, easier compared to shadow-cljs, then I don't write shadow-cljs.edn
when I have a REPL
I sometimes use lumo run a script to generate shadow-cljs.edn
😛
for example:
@bolasblack I don’t quite understand what the purpose of this script is, if you have many different namespaces you want to have accessible via require
then use :npm-module
by default it compiles file to you can require("shadow-cljs/your.app").some_function()
the purpose of :target :node-library
(which you seem to be using behind shadow-clj-build/custom
) is to condense all namespaces down a more manageable public “API”
put a package.json
in that directory with a "main":"./your.app.js"
and publish that to npm
or you can of course just require("./relative-path-to/your.app")
by setting :output-dir
so something other than node_modules/shadow-cljs