Codync
무료 오픈소스 1:1 대안, Grok Bot과 Muse 대신
개인 계정의 공개 저장소 소유자는 GitHub로 로그인해 운영자를 확인하고 소개를 직접 관리할 수 있습니다. 관리자 승인은 필요하지 않습니다.
로그인한 뒤 확인 파일을 만들어 이 저장소의 기본 브랜치에 30분 안에 커밋해 주세요. 다른 브랜치나 포크의 파일은 인정하지 않습니다. 파일을 올린 뒤 아래에서 확인하면 관리자 승인 없이 관리할 수 있습니다. 자격을 유지하려면 파일을 남겨 두세요.
로그인이 필요하면 로그인 화면으로 이동합니다. 로그인 후 이곳으로 돌아와 원하는 확인 버튼을 다시 눌러 주세요.
프로젝트 폴더에서 /nomorevibe verify를 실행하면 소유권을 확인하고 소개를 직접 관리할 수 있습니다.
1분 만에 확인하기Cargo like build tool and package manager for Kotlin
저장소 README에서 가져옴
README 전체를 불러오는 중입니다.
README 전문 보기 ↗Kargo is Cargo for Kotlin. One kargo.toml and one CLI create, build, run, test and publish Kotlin projects for the JVM, WebAssembly, JavaScript, Kotlin/Native and Android.
$ kargo new hello && cd hello
Created application `hello` package
$ kargo run
Compiling hello v0.1.0 (jvm)
Finished `dev` profile [unoptimized + debuginfo] target(s) in 2.47s
Running `java com.example.hello.MainKt`
Hello, Kotlin!
$ kargo test
No Gradle scripts, no plugins to wire up. If you have used Cargo, you already know how it works.
curl -fsSL https://enekocm7.github.io/kargo/install.sh | sh # Linux and macOS
irm https://enekocm7.github.io/kargo/install.ps1 | iex # Windows
You don't need Rust or a JDK: Kargo downloads a JDK when you have none. Nix, cargo binstall, cargo install and the other options are in the installation guide. Update later with kargo self update.
kargo.lock pins every resolved version and the SHA-256 of every artifact and tool.kargo.toml and drives the Android Gradle Plugin for you.kargo add, kargo tree, kargo why, workspaces, tasks and kargo-<name> plugins.kargo.toml[package]
name = "hello"
version = "0.1.0"
group = "com.example"
[kotlin]
version = "2.4.21"
[target.jvm] # no [target] at all means a JVM project
[target.wasm] # add more targets with `kargo target add`
[frameworks]
serialization = true
coroutines = true
[dependencies]
"org.jetbrains.kotlinx:kotlinx-datetime" = "0.7.1"
Every key is in the manifest reference.
| Target | What you get |
|---|---|
| JVM | Kotlin and Java sources, fat jars, zip/tar distributions, R8, jlink images, GraalVM native images and installers |
| WebAssembly | Node.js, WASI and browser apps (bundled with bun or Rollup), or npm libraries |
| JavaScript | Kotlin/JS for Node.js and browsers, ES, CommonJS or UMD modules with TypeScript declarations |
| Kotlin/Native | Executables and libraries for Linux, macOS, Windows and iOS, with C interop and XCFrameworks |
| Android | Apps and libraries through the Android Gradle Plugin, with flavors, signing, devices and emulators |
Built-in frameworks add their libraries, compiler plugins and flags with one line: serialization, coroutines, compose (desktop, web, iOS and Android), ktor, spring-boot, lombok and benchmark. Start from one with kargo new my-app --with ktor.
| Command | What it does |
|---|---|
kargo new <dir> | Create a project (--lib, -t jvm,wasm,js,native,android, --with compose,ktor,..., or --template <git URL or path> for your own) |
kargo build | Compile every target (--release for an optimized build) |
kargo run | Build and run the program, or serve a browser app (--watch restarts it on changes) |
kargo test | Compile and run the tests of every target (--suite integration for integration tests, --coverage for JVM code coverage) |
kargo add <group:artifact> | Add a dependency, at its latest version unless you give one |
kargo package | Build a fat jar, a runtime image, a native image, an installer or Android bundles |
kargo publish | Publish a library to Maven Central, a Maven repository or npm |
kargo import | Convert a Maven, Gradle or Kotlin Toolchain project (--keep-layout keeps the sources where they are) |
There are many more: check, coverage, fmt, lint, doc, tree, why, audit, bench, script for single files, and others. See the commands reference, or run kargo --list.
kargo lsp for every other editor.kargo import converts your project. See migrating from Gradle, from the Kotlin Toolchain and the feature parity table.Issues and pull requests are welcome. Found a bug? Run kargo report in the project: it writes a redacted report (versions, kargo.toml, the last failed build and kargo doctor) that you can paste into an issue, and kargo report --open opens a prefilled one. Nothing is uploaded.
Kargo is written in Rust:
cargo build
cargo test --workspace
The contributing guide covers the architecture, the end-to-end tests, the editor plugins, the website and releases.