Why was this change introduced? <https://github.com/JetBrains/kotlin-wrappers/commit/fdb3bad0ef88566...

# react

[Robert Jaros]

Why was this change introduced?
https://github.com/JetBrains/kotlin-wrappers/commit/fdb3bad0ef88566ffb857323630fbd1002613caa#diff-bd3e93f85ad37698fd0a6ac70811de3de7794a05add52da53ae6965f6f00cf52

[Robert Jaros]

@Leonid Khachaturov

[Robert Jaros]

I can't use kotlin-react from my UMD module

[turansky]

Do you need umd for Kotlin or for Webpack?

[turansky]

It works fine in scheme:
Kotlin - commonjs
Webpack - any format

[Robert Jaros]

It's for KVision module and whole KVision is UMD.

[Robert Jaros]

I don't even know if I could configure a single submodule for commonjs.

[Robert Jaros]

But it would still be not compatible with existing apps which use umd.

[Robert Jaros]

There is no comment and no issue linked with this commit. It would be nice to know the rationale behind this change.

[turansky]

For now - commonjs for libraries (for apps too) single valid variant, which I see.
@JsNonModule doesn’t work in common case (example).

Additional point - future ES6 modules, which also modular.

[turansky]

It would be nice to know the rationale behind this change.

@Robert Jaros We will add it README

[Sebastian Aigner]

@Robert Jaros after internal discussion, we’ve reverted this change and will publish with UMD starting again in the next version. https://github.com/JetBrains/kotlin-wrappers/commit/92b3c1b7d5499eac9a85158c0657a8872b3b96ad. Apologies for the hassle.