Reusing available published dependencies from dependencies

[nathanfallet]

I have a Kotlin library with multiple modules, with dependencies between them.
Currently, when I publish them to npm, each one gets all its dependencies bundled into the package.

Is there a way to avoid this, and use existing published npm packages instead as dependencies?

Example:

• I publish my core module to npm as @org/core.
• I have another module something that depends on core module. It gets published as @org/something
  I would like @org/something to depends on @org/core, instead of it being independent and bundle core inside of itself.

[mpetuska]

I'm afraid not as this is a long standing kotlin/js limitation (there are multiple issues for this on their youtrack).

If you really want separate module publications, you could not have them depend on each other directly but rather depend on their compiled js outputs via dependency(npm("","")). However to get this to work locally you'd need to setup local npm registry for development and publish to it each time you make changes to a module which is depended on by other modules. Not to mention erasing all kotlin interop between modules as now each imported module dependency would get raw js treatment.

[nathanfallet]

@mpetuska Do you have links to youtrack issues? I'm willing to follow and contribute, but I cannot find it.