I'm working on a multiplatform project where I gen...

# javascript

[gbaldeck]

I'm working on a multiplatform project where I generate the Kotlin/JS files using the DCE with source maps enabled. I then use webpack to pick up those files as modules and bundle them along with my modules in the node_modules directory. The issue I'm having is getting webpack to pick up the kotlin source maps. Anyone know how to do that?

[gbaldeck]

Problem solved, I discovered source-map-loader

[hallvard]

This use of webpack and all ... it wouldn't happen to be in a multiplatform project built on a 1.3-rc variant, would it? (I'm strugling to find out how to do this ...)

[gbaldeck]

@hallvard Yeah it is. As of last night my whole project is setup with everything working. Is there something in particular you're having trouble with?

[hallvard]

Nah ... I'm postponing the webpack part. But I get this funny error when doing `gradle publish`: Invalid publication 'kotlinMultiplatform': groupId cannot be empty.

[hallvard]

Funny thing is, groupId must be specified allright, because the jvm and js targets are indeed published to my maven server just before this error occurs ...

[gbaldeck]

Are you working on a multiplatform library?

[hallvard]

Yes, and I am using the newest 1.3-rc stuff permitting to have everything controlled from one gradle spot (i.e. sub-projects js and jvm defined in the same, top-level gradle file), and mostly, it works like a charm. So it's not a big deal. But that said, I would like gradle publish to work properly too ... Do you use the maven-publish plugin? Should I define somehow that it is OK not to publish the common source set? That's my theory, in fact, that gradle tries to publish stuff from jsMain, then from jvmMain and finally from commonMain ... But I don't know where to interrupt this behaviour ...

[gbaldeck]

Maybe someone from JetBrains can help with this, @bashor. I have not published any libraries using the gradle plugin for a long time so I'm not the best person to answer this