Hello! What is the difference between: ```kotlinx....

# javascript

[Rafał Kuźmiński]

Hello! What is the difference between:

kotlinx.browser.window

and

web.window.window

Which of those "windows" should we use? I see that is not just different import, those objects provides different methods

[Artem Kobzar]

I'm not sure we have web package in the standard library. Do you have some third-party library for adding such a package?

[Rafał Kuźmiński]

it comes from jetbrains.kotlin-wrappers:kotlin-browser-js

[Artem Kobzar]

@turansky ^^

[turansky]

For all stable browser API - web.window.window

[Rafał Kuźmiński]

so kotlinx will be deprecated?

[Edoardo Luppi]

If you mean kotlinx-browser, those are for the wasmJs target

[Rafał Kuźmiński]

Yes, I mean kotlinx.browser. It is available in js target for browser, not only in wasmJs

[Edoardo Luppi]

Ah now I get what you mean.
Those declarations come from the kotlin-dom-api-compat library, which is included by default alongside the stdlib.

What I'd do is exclude kotlin-dom-api-compat with

kotlin.js.stdlib.dom.api.included=false

and use kotlin-browser from kotlin-wrappers, as you're already doing, it seems.

[Rafał Kuźmiński]

this line will exclude web.window or kotlinx.browser.window?
kotlin.js.stdlib.dom.api.included=false

[turansky]

Also IDEA exclude we use

[Rafał Kuźmiński]

Thanks, I'll check it out

[Edoardo Luppi]

I've quickly tested kotlin.js.stdlib.dom.api.included=false as I've last used it a long time ago.

Strangely enough, I can still compile with a function like

fun dummy() {
  kotlinx.browser.window
}

But if I try to use org.w3c.dom.XMLDocument, which also comes from the compat library, it errors out.

[turansky]

It excludes org.w3c and org.khronos.* only

[Edoardo Luppi]

Ah, didn't know that! Why?

[turansky]

Because no issue 🙂

[Edoardo Luppi]

Looks like I'll have to create an issue then