fwcd / fwcd/kotlin-language-server
Supper non-JVM backends (Kotlin/Native, Kotlin/JS, Kotlin/Wasm)
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 2k
- Forks
- 252
- PR merge metrics
- No merged PRs in 30d
Description
Support non-JVM backends, such as...
- Kotlin/Native: https://kotlinlang.org/docs/native-overview.html
- Kotlin/JS: https://kotlinlang.org/docs/js-overview.html
- Kotlin/Wasm: https://kotlinlang.org/docs/wasm-overview.html
The native backend might be particularly interesting for iOS/Android apps using Compose Multiplatform, while the JS/Wasm support would be cool for using Kotlin in (web) frontend projects.
The kotlin-compiler-server used by the kotlin-playground (hosted on https://play.kotlinlang.org), provides a nice reference implementation for JS and Wasm and would be worth studying.
Since the language server itself (mostly) just depends on the compiler frontend, integrating dependency resolution would be the central challenge.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by studying the kotlin-compiler-server reference implementation used by kotlin-playground, focusing on its JavaScript and Wasm support. Investigate how the language server’s compiler frontend and dependency resolution would apply to Kotlin/Native, Kotlin/JS, and Kotlin/Wasm. Done means the listed non-JVM backends are supported by the language server.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kotlin, wasm
- Domain
- devtools, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100