ok, current state to the aforementioned problems: ...

# javascript

[thana]

ok, current state to the aforementioned problems: the function thrown out by the terser plugin was named "initialize" which is the root of all evil. the method must not be named so, it must have a different name, then all is fine.
this js stuff is so incredibly crappy

[Marc Knaup]

That’s why there is a new compiler front-end called IR in the works 😅
But it also has its moments…

[thana]

well dont think the IR compiler can help here. its clearly an issue in the js tooling not kotlin's/jetbrain's fault

[Marc Knaup]

Why the JS tooling? The Kotlin/JS compilers are known to have issues if symbol names collide or are reserved keywords.

[thana]

because the function still exists in the dce variant before it's passed to the terser plugin

[Marc Knaup]

The KJS stack uses a rather old version of Webpack and Terser.
I’ve manually updated Terser in my stack which solved a lot of issues.

[thana]

well that might be a point. still i dont get why on earth an even an ancient version of the terser would deliberately remove a function called 'initialize' but keep the very same version as soon as it's called 'initialisieren'

[Marc Knaup]

is there any other symbol that may have a conflicting name? ¯\_(ツ)_/¯

[thana]

mmh wouldn't js fail on it? the method itself is in use for almost 2 years now

[Marc Knaup]

No, I mean if another variable or function with the same name accidentally hides your inititalize function, your function would be unused and thus be removed. But it’s just one of many possible theories.

[thana]

nope, dont think so