After adding a dependency to apollo-testing-support it can’t find kotlinx-nodejs:0.0.7 anymore. It s...

# apollo-kotlin

[Stylianos Gakis]

After adding a dependency to apollo-testing-support it can’t find kotlinx-nodejs:0.0.7 anymore. It seems like that’s because that library is still hosted only on jcenter() despite it shutting down soon. So luckily it solves itself if I add jcenter() in the list of repositories, despite having the IDE yell at me for it 😅

Is this something worrisome? And if yes, is the only solution possible to come from JetBrains themselves publishing their library somewhere else as well, or do you have plans to somehow not depend on that one in that artifact anymore at some point?

Also maybe a gotcha for someone who might add the dependency and get confused why it doesn’t work, idk if it’d fit your documentation really, but it’d suck for someone who wouldn’t know how to resolve this.

[mbonnin]

Upvote https://github.com/Kotlin/kotlinx-nodejs/issues/16

[Stylianos Gakis]

Thanks, will do!

[mbonnin]

apollo-testing-support is still pretty young and unstable so there's not much documentation about it yet. I'm hoping once it gets more stable and we start writing docs, the nodejs artifacts will be published to central

[Big Chungus]

Also jcenter is now read-only indefinitely and will not be closing. Although it's unstable as fuck, so everything should still be migrated out of it asap.

[Stylianos Gakis]

Yeah it makes sense. Btw Martin when you say young and unstable I am assuming you then mean both in terms of potential breaking API changes and potential general stability issues or only one of them? If it’s either, do you think it’d be worth a spot in the docs here to denote that stability level?

[mbonnin]

There's a @ApolloExperimental annotation but adding a note in the docs wouldn't harm either!

[mbonnin]

It's mostly about potential API changes and getting more feedback until it's promoted stable and we can't change anything anymore