A modern programming language that makes developers happier.

kotlinlang

Hi regarding <https://youtrack.jetbrains.com/issue/KT-43237>, are there more people affected? In our case we need to do a somewhat orthodox workaround renaming the imports to the affects js libs.

_“KJS: `-jsLegacy` Naming Convention is incompatible with NPM_

_Libraries such as `kotlinx.serialization` are exporting artifacts with a `-jsLegacy` suffix when using the legacy compiler with Kotlin 1.4. NPM however, doesn’t allow capital letters in package names.”_

That would be great if that could be fixed.

<@UJRUJP0F9> what do you think? :slightly_smiling_face:

Can’t tell anything specific right now. Got to ask my teammate tomorrow.

Hi, thanks,
It is necessary to fix, but unfortunately I am not sure, that it will be fixed in next release (1.4.30)
But if you affected by your own generated js file, you can use `moduleName`
For example:

```kotlin {
  js {
    moduleName = project.name
  }
}```
But unfortunately it is not so useful for external dependencies

Is there anything we can do? if it’s an easy fix then we can perhaps create a PR? :slightly_smiling_face:

It is something like `decamelize`
I have already made <https://github.com/JetBrains/kotlin/commit/f2daeb78c2c1f850ceebd13898aaf8ee2c64b670|commit>
Now it is testing

So we can perhaps get it in 1.4.30? :slightly_smiling_face: . Ship it. :ship:

I can test it tomorrow if you provide the artefact or instructions how to compile it :slightly_smiling_face: .

&gt; So we can perhaps get it in 1.4.30?
I am afraid, that not, release cycle of 1.4.30 already is in progress (1.4.30-M1 already released :slightly_smiling_face: )
Another one problem, that I want to investigate effect of this change in term of compatibility (in fact it can be problem, because file name is important in js ecosystem)

&gt; I can test it tomorrow if you provide the artefact or instructions how to compile it 
If I understand you correctly, it is important for you to get correct names of kotlin libraries (kotlinx.serialization e.g.), and it can will be ok only after republishing of such libraries (and it will be in their corresponding release cycles)

If you only need to change your own names, you can use `moduleName` in your projects

&gt;  If I understand you correctly, it is important for you to get correct names of kotlin libraries (kotlinx.serialization e.g.), and it can will be ok only after republishing of such libraries (and it will be in their corresponding release cycles)
yeah thats correct. :slightly_smiling_face: .

&gt; If you only need to change your own names, you can use `moduleName` in your projects
We’re aware of that setting :slightly_smiling_face: .

Yeah ok but when you use ktor you will have the same Problems.

<@UAG4QQZB6> in which version will be the decamelize feature?

It should be in 1.5.0 releases (1.5.0-M1, 1.5.0-M2 and so on)

M1 (milestone-1) is already released, and bug is fixed in it
M2 should be in near future, but we don’t provide concrete estimates