This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-04-19
Channels
- # aws-lambda (4)
- # beginners (62)
- # cider (20)
- # cljs-dev (9)
- # cljsrn (13)
- # clojars (3)
- # clojure (105)
- # clojure-brasil (1)
- # clojure-denver (1)
- # clojure-finland (4)
- # clojure-italy (23)
- # clojure-norway (1)
- # clojure-spec (6)
- # clojure-uk (56)
- # clojurescript (41)
- # cursive (10)
- # datomic (25)
- # emacs (23)
- # figwheel (2)
- # fulcro (133)
- # graphql (12)
- # hoplon (32)
- # instaparse (13)
- # keechma (1)
- # lein-figwheel (1)
- # luminus (1)
- # lumo (1)
- # nyc (2)
- # off-topic (34)
- # om (2)
- # onyx (10)
- # pedestal (8)
- # portkey (1)
- # re-frame (10)
- # reagent (26)
- # ring (8)
- # shadow-cljs (77)
- # spacemacs (4)
- # sql (8)
- # tools-deps (15)
- # vim (9)
for deps.cljs
files, I'm reading that :foreign-libs
and :npm-deps
are inherited from 'upstream', but this is usually in the context of jars. Does all the same language apply/work for cljs.main
and gitlibs?
and are there any differences in general with how deps.cljs
works with deps.edn
based projects, compared to the jar scenarios discussed in the existing docs?
Yeah, and I thought I heard folks discussing deps.cljs
in the context of cljs.main
in here a few weeks ago. Just making sure.
hmm, in a mono repo like setup, with deps.cljs
in a particular module's src folder, I'm not seeing that the compiler is noticing the file there. The documentation states that the code-split-module system works with the :foreign-libs
. I'm testing externs currently, which can also go in that deps.cljs
file, but externs are only getting processed when declared from my min.co.edn
file passed to -m cljs.main -co ...
.
I'll check jira tonight and try to see if I'm doing something wrong or if there's a bug there