cljsjs

2016-11-24T06:57:10.001193Z

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

juhoteperi 2016-11-24T07:00:15.001200Z

@biscuitpants Just a message here is enough 🙂

2016-11-24T07:00:33.001201Z

oh sweet 😄

2016-11-24T07:00:34.001202Z

thank you

2016-11-24T07:01:22.001204Z

thank you for merging those!

2016-11-24T08:36:47.001208Z

so question about cljsjs

2016-11-24T08:37:37.001209Z

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

2016-11-24T08:37:37.001210Z

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

juhoteperi 2016-11-24T08:40:10.001211Z

not using the default packages

2016-11-24T08:40:29.001212Z

poo

juhoteperi 2016-11-24T08:40:30.001213Z

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

juhoteperi 2016-11-24T08:40:46.001214Z

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

2016-11-24T08:41:04.001215Z

so have a v3 extern and v4 extern?

juhoteperi 2016-11-24T08:41:26.001216Z

yeah I think that would work

2016-11-24T08:41:31.001217Z

let me try that, thanks

juhoteperi 2016-11-24T08:42:18.001220Z

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)

juhoteperi 2016-11-24T08:42:37.001221Z

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

juhoteperi 2016-11-24T08:43:03.001222Z

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

juhoteperi 2016-11-24T08:43:22.001223Z

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

2016-11-24T08:44:48.001224Z

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