Is there any difference between kt or kts file format for convention plugins in includeBuild project?

.kts is usually for "precompiled scripts plugins", they use the same Kotlin syntax as "regular"

build.gradle.kts

files (sam with receiver for

Action<T>

, assignment plugin, generated accessors, etc...) I use

.kt

all the time because I find it easier to understand how the API work under the hood this way.

Yeah but at the same time it becomes more hard to understand for developers who not familiar with this API, underlying extensions etc. and more familiar with API’s they use in build.gradle.kts. So my thought process maybe it’s better to write convention plugins in kts files so it will be more accessible for other developers. My main concerns with kts: • Is there any limitations in gradle API usage • Any compilation speed or caching issues

precompiled script plugins are slower

Personally I like to recommend

.kts

for convention plugins and

.kt

for "regular/other" plugins

I think

.kts

is really more of an habbit. In a declarative Gradle world, there is very little upside to using

.kts