This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-11-24
Channels
- # arachne (1)
- # bangalore-clj (11)
- # beginners (177)
- # boot (63)
- # business (1)
- # cljsjs (21)
- # cljsrn (3)
- # clojars (4)
- # clojure (116)
- # clojure-art (4)
- # clojure-belgium (3)
- # clojure-india (1)
- # clojure-italy (6)
- # clojure-russia (14)
- # clojure-spec (8)
- # clojure-uk (67)
- # clojurescript (51)
- # community-development (5)
- # cursive (13)
- # datascript (14)
- # datomic (29)
- # devcards (3)
- # emacs (3)
- # events (3)
- # funcool (4)
- # hoplon (29)
- # mount (6)
- # om (34)
- # om-next (5)
- # onyx (16)
- # perun (8)
- # planck (22)
- # re-frame (13)
- # reagent (5)
- # ring-swagger (21)
- # rum (3)
- # spacemacs (3)
- # specter (1)
- # untangled (39)
who should i ask about PR’s? as in confirming them, to be merged in
@biscuitpants Just a message here is enough 🙂
oh sweet 😄
thank you
thank you for merging those!
so question about cljsjs
is it possible, to have one version of a lib as a dependency, and another version as a separate externs file?
for instance, d3.v3
as an externs, and d3.v4
as a dep?
not using the default packages
you can't depend on two versions with same artifact id
but you could easily just copy the d3 version 3 extern to your project
so have a v3 extern and v4 extern?
yeah I think that would work
let me try that, thanks
I think you'll need to change the path for this and add a deps.cljs
to your project (classpath root, e.g. resources/deps.cljs
)
deps.cljs just need {:externs ["path/to/extern/in/classpath.ext.js"]}
if you only wanted to have v3 externs, it might work that you place the v3 extern to same path in your project as it is in the cljsjs package
e.g. resources/cljsjs/d3/common/d3.ext.js
, that might then overwrite the file from cljsjs package, but I'm not sure
hmm, so running a v3 and v4 externs file still gets the clash, which is weird