This is more the kind of projects impacted by the explicit library mode, and for this one, public won't be as prevalent as you seem to imply.

In this case, you most likely don't want to expose your JS dependencies' API transitively, and will stick to internal.

you write a multiplatform or JS library and use NPM dependencies with externals.

This one will mainly have everything public, yes, but I don't think this is the kind of project that would benefit from this explicit library mode, so you would probably not turn it on anyway. Visibility modifiers are keywords that set the visibility (accessibility) of classes, objects, interface, constructors, functions, properties and their setters.

you declare externals in a single module to be reused in other projects, just like you would publish the typescript definitions for an NPM package. Kotlin Visibility Modifiers In this article, you will learn about all 4 visibility modifiers in Kotlin and how they work in different scenarios.

There is actually 2 main use cases I can see so far: The nature of external declarations is to make JS code available to Kotlin code. How are external declarations in any way special compared to the other declarations?īecause they by their nature in 99% percent of cases supposed to be I don't really get your point here.

Visibility modifiers in kotlin