Another technical question. Looking at the outputted JS with ES modules I see: ```var MainTestClass;...

# javascript

[Edoardo Luppi]

Another technical question. Looking at the outputted JS with ES modules I see:

var MainTestClass;
function MainTest() {
  if (MainTestClass === VOID) {
    class $ {
      constructor() {
        return new.target.new_MainTest_jncw2x_k$();
      }
      static new_MainTest_jncw2x_k$($box) {
        return createThis(this, $box);
      }
      main() {
        init();
      }
    }
    initMetadataForClass($, 'MainTest', $.new_MainTest_jncw2x_k$);
    MainTestClass = $;
  }
  return MainTestClass;
}

Where, to generate the actual class, the function MainTest() is called.
Why is it wrapped in a function? This doesn't seem to happen when targeting CommonJS.

[turansky]

AFAIK It's required for Kotlin initialization logic emulation

[turansky]

@Artem Kobzar ^^

[Edoardo Luppi]

I'm just surprised it's only for ES modules.

[turansky]

With file-to-file we receive 2 exports
1. Export in Kotlin
2. Export in JS

[turansky]

And they don't work same way

[Edoardo Luppi]

But this happens even for per-module. Did a bunch of tests to understand if it was connected to granularity, and it doesn't seem to be so

[turansky]

In common case it's ES modules specific

[Artem Kobzar]

It's only for per-file to work with circular-dependencies between files + it should improve tree-shaking of the classes.

[Edoardo Luppi]

Thanks! I'll try again with per-module then, because IIRC it did happen with that too