I'm experimenting with extracting common logic into a common kotlin module, which I then compile to Javascript and want to consume in a typescript project (as an npm module). The dependency via NPM works, but I am unsure as to where I would put my typescript definition files. Tried putting them in

jsMain/resources

, but those files never show up in the NPM project that's generated by the gradle plugin. Moreover: I am applying the "multiplatform" plugin in a subproject, but the javascript npm projects are still generated in the top level project build folder and there is also an NPM project generated for the top level project (which does not have the multiplatform plugin!). The NPM project that actually contains my js code is put into

build/js/packages/<root project name>-<subproject name>

. How can I disable this? I just want a plain NPM project for the javascript code.

Unforunately, now there is no possibility to include some addtional files to build directory of Kotlin/JS output. All resources are processed in module build directory in

processedResources

As for your second question, there is some reasons, why we choose this kind of layout. In case of multiple Kotlin/JS modules, there is only one root

node_modules

, that are shared betwen all packages without duplication It is related with how node resolve their modules We discuss it recently in #javascript https://kotlinlang.slack.com/archives/C0B8L3U69/p1570548676169100?thread_ts=1570132203.140300&cid=C0B8L3U69

I am unsure as to where I would put my typescript definition files

@diesieben07, as @Ilya Goncharov [JB] said it is not supported yet. Please create issue in http://kotl.in/issue

also an NPM project generated for the top level project

It doesn't. Top-level package.json is not related to any Gradle project. It just contains list of workspaces that located in

build/js/packages

and

build/js/packages_imported

. If you will apply kotlin multiplatform or js plugin to root project, corresponding npm package will be created in

build/js/packages

, not in

build/js

.

How can I disable this? I just want a plain NPM project for the javascript code.

We can make special layout for it, but in this cases yarn workspaces and shared npm dependencies will not work for subprojects with this layout. What is your use case? Do you really need it?

I don't mind NPM workspaces. But what happens is the following:

|_build <- I get an NPM project here! for the root project AND the `mpp` project.
|_build.gradle // plugin multiplatform and jvm with apply false
|___server
    |___build.gradle // plugin jvm, depends on :mpp
|___mpp
    |___build.gradle // plugin multiplatform
    |___src/commonMain/kotlin
    |___src/jsMain/kotlin
    |___src/jvmMain/kotlin

There is no way to get multiple NPM projects working together without placing them in some directories with single common

package.json

. That's why the output of all subprojects are located in the root's project build directory.

I wouldn't mind the npm project in root build. What I do mind is that I get an NPM project for the root gradle project, even though it does not have the MPP or JS plugins applied.

Can you please share your project?

I am in a meeting until lunch, but I will share an example project in a few hours.

For now, it is more like implementation detail, yes. But we are planning to support projects with manually created NPM packages too. There is some way to get it working in the current implementation too, but it is hacky: you may create your own

package.json

in the root (not in root/build) with

"workspaces": ["build/js/packages/*", "build/js/packages_imported/*", path-to-you-package-here]

. In this way you can just

import {foo} from "sub-project"

Thank you, I will do some experimentation with that.

@diesieben07 Here is an example with a workaround for using Kotlin/JS from pure JS module using current Gradle Kotlin/JS plugin: https://github.com/diesieben07/kotlin-mpp-npm-demo/pull/1. See README.md for more details. We are planning to support this layout (or something like this) in our Gradle plugin, but probably it will not very soon. There are many things that we want to fix for the simple "getting started" scenarios first...

Thank you very much for your work, that looks promising. I will check it out in detail this evening.