Publish idiomatic packages for non-Kotlin / non-Gradle usage
Open
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 200
- Forks
- 45
- PR merge metrics
- No merged PRs in 30d
Description
- Java-friendly API on the JVM Maven package
- Swift package for apple native builds
- NPM package with TS declarations for JS
- C headers for native builds? Investigate packaging conventions here
- WASM package isn't possible due to
@JsExportrestrictions.
Contributor guide
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
The issue names no files or tests. Start by reviewing the existing JVM Maven package and NPM package with TypeScript declarations, then investigate Swift package and C header conventions for native builds. Done means the remaining packaging work is implemented or its feasibility and conventions are documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, kotlin, swift, typescript
- Domain
- build-system, developer-experience, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100