for some reasons. ```kotlin { browser {} node...
# javascript
a
for some reasons.
Copy code
kotlin {
  browser {}
  nodejs {}
}
seems more intuitive and inline with KMM than
Copy code
kotlin {
  js {
    browser()
    nodejs()
  }
}
The former unlocks • hierarchical source sets between javascript targets • Easier gradle resolutions for browser or node specific • Intrinsically adding
kotlinx-browser
and
kotlinx-node
depedencies
4
c
I guess it makes sense, but what happens when WASM comes along? Does it take over
browser
?
a
@CLOVIS when wasm will be
Copy code
kotlin {
  browser{}
  wasm{}
}
c
Yeah but that's weird for new users, that if they want to write something in WASM for browser it's not with
browser
. I like the above issue though:
Copy code
kotlin {
  jsBrowser()
  jsNode()
  wasm()
}
a
I get your point now