I was looking at <https://youtrack.jetbrains.com/i...
# multiplatforme
Edoardo Luppi
10/02/2023, 1:31 PMI 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 project structure solves the JS Node != Browser issue?
Or maybe I just misunderstood the use case.
👀 1
m
mbonnin
10/02/2023, 3:30 PMI thought Node vs Browser was only a test thing?
e
Edoardo Luppi
10/02/2023, 3:31 PMWell not really. For example, major issues comes up with HTTP APIs, or XML manipulation.
Node doesn't have a DOM model
Edoardo Luppi
10/02/2023, 3:32 PMSo every time you need to conditionally understand if you're under Node or not.
m
mbonnin
10/02/2023, 3:32 PMI see. Welp yea, sounds like they should be different targets, just like watchos and ios are different targets 🤔
e
Edoardo Luppi
10/02/2023, 3:32 PMExactly, 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
Edoardo Luppi
10/02/2023, 3:33 PMAnd a "commonJsMain" source sets for both.
2 Views