I was looking at https://youtrack.jetbrains.com/issue/KT-61007 I'm trying to understand the why of multiple targets, or multiple compilations, of the same type. Wondering if multi-compilation with the new hierarchical multiplatform configuration solves the JS Node != Browser issue? Or maybe I just misunderstood the use case. Shipping for both Node and the browser is still a problem if done on the same project.

I thought Node vs Browser was only a test thing?

Well not really. For example, major issues comes up with HTTP APIs, or XML manipulation. Node doesn't have a DOM model

I see. Welp yea, sounds like they should be different targets, just like watchos and ios are different targets 🤔

Exactly, but this has been open for ages. In the meantime I was really wondering if a workaround might be different compilations with different source sets