When distributing a

library

that depends on e.g.

org.jetbrains.kotlin-wrappers:kotlin-react-dom

, is there are way to automatically populate transitive NPM dependencies in

package.json

? So that I can avoid adding

implementation(npm("react-dom", "*"))

explicitly.

npm-publish plugin used to do that in early versions but then I dropped it when binaries.library came along as it was not needed anymore. However I kinda assumed that transitive npm dependencies would get propagated into pjson... Looks like I'll need to bring that feature back tomorrow

My use case is, after running

browserProductionLibraryDistribution

I need to

webpack

the output. I need all transitive NPM dependencies to be present in

package.json

. Currently I'm adding them manually, which is error prone. It's also not straight forward as I need to guess what Kotlin wrapper belongs to what NPM module (or multiple modules). E.g. it's not clear what NPM module(s) should I add if I use

kotlin-emotion

.

I'm aware 😀

I am also currently doing this. Adding npm dependencies all by myself on the final libary. For me, I am lucky all I need to do is add react, platform and joda-time, but I know it can explode with just a single extra add on

No, this is more bug than intentional behaviour And that’s one of reasons why we do not announce this feature 🙂

Ah, awesome. I'll raise a pr to kgp then

I believe this one https://youtrack.jetbrains.com/issue/KT-45789/KJS-IR-Transitive-NPM-dependencies-are-not-included-in-PublicPackageJsonTask-output

upvoted faster than the flash

There we go https://github.com/JetBrains/kotlin/pull/4888