kscript VS Fuel

You probably want to have a look at kscript. It's fixes the primary issue of kotlin script (uncompetitive startup time) by adding a cache of compiled scripts: https://github.com/kscripting/kscript

There is a community project called kscript, which can execute bare bones kotlin script files. The shebang line for that would be #!/usr/bin/env kscript. While that is one thing which can be done with Kotlin script, it is not its main purpose, its main purpose is to have a script definition in some other Kotlin program which can then execute any Kotlin script following that definition at runtime. See the official tutorial for how a Kotlin program would run such a script.

I think you can run `kscript` on windows but i didn't really tried.check out kscript

How exactly did you install sdk man? Wonder if it's configured correctly with the path. kscript had the sdkman install instructions for kotlin which was a dependency in my project

Cheers to kscript!

I am surprised not to see any mention of kscript https://github.com/holgerbrandl/kscript

and the community-led kscript effort.

That kinda reminds me of Fuel https://github.com/kittinunf/fuel

But when I started to use it, I faced an issue. In a traditional Maven project, the workaround would be to add the dependency in the available version, and thus override the default one. Yet, it doesn't work with Kotlin Scripting - it's not possible to override versions in the same way.