Fork me on GitHub
#cljsjs
<
2016-11-24
>
biscuitpants06:11:10

who should i ask about PR’s? as in confirming them, to be merged in

juhoteperi07:11:15

@biscuitpants Just a message here is enough 🙂

biscuitpants07:11:33

oh sweet 😄

biscuitpants07:11:22

thank you for merging those!

biscuitpants08:11:47

so question about cljsjs

biscuitpants08:11:37

is it possible, to have one version of a lib as a dependency, and another version as a separate externs file?

biscuitpants08:11:37

for instance, d3.v3 as an externs, and d3.v4 as a dep?

juhoteperi08:11:10

not using the default packages

juhoteperi08:11:30

you can't depend on two versions with same artifact id

juhoteperi08:11:46

but you could easily just copy the d3 version 3 extern to your project

biscuitpants08:11:04

so have a v3 extern and v4 extern?

juhoteperi08:11:26

yeah I think that would work

biscuitpants08:11:31

let me try that, thanks

juhoteperi08:11:18

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)

juhoteperi08:11:37

deps.cljs just need {:externs ["path/to/extern/in/classpath.ext.js"]}

juhoteperi08:11:03

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

juhoteperi08:11:22

e.g. resources/cljsjs/d3/common/d3.ext.js, that might then overwrite the file from cljsjs package, but I'm not sure

biscuitpants08:11:48

hmm, so running a v3 and v4 externs file still gets the clash, which is weird