Testing with `per-file` granularity in 1.9.22, I noticed each .kt file now outputs two .js files. On...

# javascript

[Edoardo Luppi]

Testing with per-file granularity in 1.9.22, I noticed each .kt file now outputs two .js files.
One seems dedicated to exporting the other's definitions.
Has this been done recently, or was it always like that? And also, is there a technical reason for doing so?

[Artem Kobzar]

It was always to improve tree-shaking for the exported declarations (and hide some top-level effects).

[Edoardo Luppi]

@Artem Kobzar I think I didn't notice it before because I wasn't `@JsExport`ing.
That clarifies it, thanks!

[Edoardo Luppi]

I'll have to open in issue because kotlin.test tests don't work with per-file.

[Artem Kobzar]

What compiler version do you have?

[Edoardo Luppi]

1.9.22

[Artem Kobzar]

https://youtrack.jetbrains.com/issue/KT-61525

[Artem Kobzar]

It’s fixed in 2.0.0-Beta2

[Edoardo Luppi]

Ah thanks! Does it work if in 2.* I disable K2?

[Artem Kobzar]

Yeah, at least it should, if it’s not - please create an issue

[Edoardo Luppi]

Perfect. I'm blocked by a couple of YT issues unfortunately, so K1 support is always nice to have.