Is this project still relevant?

[joffrey-bion]

Given the absence of updates for years, it looks like the browser APIs are in the stdlib and not brought by this module anymore.

Is this the case? If yes, maybe this project should be archived?

I'm trying to figure out why the dom package is not found in my project, and I struggle to find information about which of dom.html or org.w3c.html or kotlinx.browser or other packages I am supposed to use. This project adds to the confusion.

[trilis]

Right, this repo probably hasn't been relevant for a long time. @bashor can you please confirm and archive it?

[ilya-g]

We still have plans to extract org.w3c and kotlinx.dom/browser packages from stdlib-js in the near future, and this repository will likely be used for that.

[joffrey-bion]

I eventually figured out that I needed web.html and web.dom over the others, but maybe this is because I'm using Kotlin/React and specifically the kotlin-wrappers.

Are you saying org.w3c.* and kotlinx.dom should still be used (or will) as part of pure Kotlin/JS?

[bashor]

Please follow this issue KT-35973 for updates.

[bashor]

I'd suggest writing relevant information to README.md and archiving the repo now. (And unarchive as soon as it is ready.)
cc @anton-bannykh @ilgonmic

[igoriakovlev]

This issue is closed because of this repository is now used for Kotlin WasmJs implementation. The Kotlin JS platform implementation we have no plans to yet.