If I m writing code that s only targeting nodeJS can I exclu

Question

If I m writing code that s only targeting nodeJS can I exclude the Browser APIs I have `kotlin dom api compat` in my dependencies but I m not sure where it s coming from

Edoardo Luppi · Answer

AFAIK it s part of the K JS stdlib `kotlin stdlib` You may be able to exclude it using the usual Gradle way

mbonnin · Answer

Was a bit afraid of that

mbonnin · Answer

Did a bit more digging looks like it s <https github com JetBrains kotlin blob f5d859f209a5991bcfa5260a0c1c23782f9d4849 libraries tools kotlin gradle plugin src common kotlin org jetbrains kotlin gradle internal kotlinDomApiDependencyManagement kt L41|added by KGP>

mbonnin · Answer

I wonder how come Browser amp Node are not different targets like iosArm64 and macosArm64

mbonnin · Answer

JS is the binary format just like mach o What APIs are available is something else

Edoardo Luppi · Answer

```project configurations all exclude group = org jetbrains kotlin module = kotlin dom api compat ``` Something like this seem to work to avoid getting it into the classpath

Edoardo Luppi · Answer

If you find out a better way let me know

mbonnin · Answer

This works too ```kotlin js stdlib dom api included=false```

mbonnin · Answer

Still this is a weird default

Edoardo Luppi · Answer

That s a lot better

Edoardo Luppi · Answer

Did you find the key in the documentation

mbonnin · Answer

Good old grep sweat smile it s <https github com JetBrains kotlin blob f5d859f209a5991bcfa5260a0c1c23782f9d4849 libraries tools kotlin gradle plugin src common kotlin org jetbrains kotlin gradle plugin PropertiesProvider kt L588|here>

Edoardo Luppi · Answer

Ahhhh good job I guess in the current JS status it s worth of a mention in the docs

mbonnin · Answer

Just realized it also relates to your <https youtrack jetbrains com issue KT 59316 Deprecate multiple same targets focus=Comments 27 8321309 0 0|comment here> Being able to have 2 sources sets with different dependencies would be cool

Edoardo Luppi · Answer

Btw thanks for this Removing that library exposed a couple of references to the browser `Document`

Edoardo Luppi · Answer

Yeah I hope the split happens soon For the piece of mind of every multiplatform library developer

Edoardo Luppi · Answer

Also the longer it takes to happen the more messier the transition conversion will be

turansky · Answer

In Kotlin `1 9 20` I also saw related task property `noStdlib`

Ilya Goncharov [JB] · Answer

Hi Indeed `kotlin dom api compat` earlier was part of stdlib and during extraction of DOM API from stdlib we were aware of backward compatibility and that s why this dependency included by defult Yes this default can be changed via `kotlin js stdlib dom api included=false` We consider possibility to change default and not include this dependency by default

Edoardo Luppi · Answer

If it s just a matter of setting `kotlin js stdlib dom api included=false` by default then I agree

Edoardo Luppi · Answer

If there is a lot of work to do I d just leave it as it is