简体中文

lucide-icon-kmp is a Kotlin Multiplatform wrapper around Lucide Icons for Compose Multiplatform. It provides a lazy icon registry, configurable LucideIcon, searchable LucideIconPicker, custom icon registration, and a build-time generator for bundled icons.

This repository is organized as a multi-module Kotlin Multiplatform build:

• lucide-core: shared icon models, metadata, lazy registry, search, and bundled icon registration.
• lucide-compose: Compose Multiplatform UI components such as LucideIcon and LucideIconPicker.
• lucide-generator: JVM generator that reads vendored Lucide SVG files and emits Kotlin source files and indexes.
• sample-compose: sample app targets that demonstrate icon rendering, picker usage, and custom icon registration.

Current publish coordinates are:

• group: com.shermant
• version: 0.2.0-SNAPSHOT
• lucide-core: com.shermant:lucide-icon-kmp:0.2.0-SNAPSHOT
• lucide-compose: com.shermant:lucide-icon-kmp-compose:0.2.0-SNAPSHOT

Public Maven coordinates use the published artifact ids above. The internal Gradle module names :lucide-core and :lucide-compose are not the coordinates you should declare in a consumer project.

For the current snapshot publish setup, the local publish environment points to:

https://central.sonatype.com/repository/maven-snapshots/

Use that repository only after your snapshot artifacts have been uploaded to Central snapshots. It is a consumer repository URL, not the primary release upload endpoint.

Example dependency setup:

repositories {
    maven("https://central.sonatype.com/repository/maven-snapshots/")
    google()
    mavenCentral()
}

dependencies {
    implementation("com.shermant:lucide-icon-kmp:0.2.0-SNAPSHOT")
    implementation("com.shermant:lucide-icon-kmp-compose:0.2.0-SNAPSHOT")
}

For local integration from another Kotlin Multiplatform project, see LOCAL_USAGE.md.

lucide-core and lucide-compose currently declare these Kotlin Multiplatform targets:

• Android
• Desktop JVM
• JS (IR)
• WasmJs
• iOS (iosX64, iosArm64, iosSimulatorArm64)

sample-compose currently includes runnable entry points for:

• Android
• Desktop JVM
• WasmJs browser
• iOS

Current gaps and caveats:

• The sample app does not currently provide a dedicated JS (IR) demo entry point.
• Library and sample modules keep their full declared target set during local and CI builds, including iOS variants.

LucideIcon(
    name = "activity",
    size = 24.dp,
    color = Color(0xFF2563EB),
    strokeWidth = 2.5f,
)

val state = rememberLucideIconPickerState()

LucideIconPicker(
    state = state,
    locale = LucideLocale.Zh,
    columns = 4,
    pageSize = 24,
    searchLimit = 100,
    iconSize = 20.dp,
    onIconSelected = { metadata ->
        println(metadata.key.value)
    },
)

LucideIcons.registry.registerCustomIcon(
    name = "brand-logo",
    tags = setOf("brand"),
    imageVector = customImageVector,
)

The repository vendors a pinned Lucide snapshot under lucide-generator/src/main/resources/lucide-icons and commits the generated Kotlin outputs in lucide-core.

./gradlew :lucide-generator:generateBundledLucide

This task regenerates the built-in registry, metadata chunks, and icon providers under lucide-core/src/commonMain/kotlin/com/shermant/core/generated.

Generated icon files are intended to be committed so consumers do not need to regenerate them during normal library usage.

The current pinned Lucide snapshot is 1.16.0; the exact tag, commit, and resource counts are recorded in lucide-generator/src/main/resources/lucide-icons/VERSION.txt.

This repository now targets Maven Central only. Use publishCentralSnapshot when VERSION_NAME ends with -SNAPSHOT.

For local publishing in this repository, keep one source of truth per config type:

• checked-in project metadata such as VERSION_NAME stays in gradle.properties
• local publish credentials stay in the root .secrets file
• .env is not part of the publish flow
• local PowerShell publishing should go through scripts/publish-central.ps1, which loads .secrets into the Gradle properties expected by the publishing plugin

Before running a snapshot publish, set your Central Portal token in .secrets:

• MAVEN_CENTRAL_USERNAME
• MAVEN_CENTRAL_PASSWORD

Because these publish tasks include Android publications, configure a local Android SDK before running them:

• add sdk.dir=... to a local root local.properties file
• or set ANDROID_HOME / ANDROID_SDK_ROOT in your shell environment

Signing is optional for snapshots. If you want to sign snapshot artifacts locally, add these to .secrets:

• SIGNING_KEY_BASE64 / SIGNING_PASSWORD

Publish a snapshot with:

./gradlew publishCentralSnapshot

Public snapshots that include Apple variants must be published from a macOS host or macOS CI. Do not publish public snapshots from Windows because they can miss iosArm64 and iosSimulatorArm64 artifacts.

The repository now includes a macOS GitHub Actions workflow at .github/workflows/publish-central.yml as the standard public snapshot entry point.

The task fails early if the version is not a snapshot, if the Central token is missing, or if the host is not macOS.

Use publishCentralRelease when VERSION_NAME is a formal release without the -SNAPSHOT suffix.

Formal releases require all of the following:

• a verified Central Portal namespace for com.shermant
• Central snapshots enabled if you also want snapshot uploads
• a Central Portal user token, not your website login password
• signing credentials for all release artifacts

Recommended credential sources are:

• local .secrets with MAVEN_CENTRAL_USERNAME, MAVEN_CENTRAL_PASSWORD, SIGNING_KEY_BASE64, and SIGNING_PASSWORD
• CI or automation can still use environment variables when needed

Configure a local Android SDK before running the release task because the publication graph also resolves Android artifacts:

• add sdk.dir=... to a local root local.properties file
• or set ANDROID_HOME / ANDROID_SDK_ROOT in your shell environment

Publish and auto-release through Central Portal with:

./gradlew publishCentralRelease

This build validates the release mode before upload:

• VERSION_NAME must not end with -SNAPSHOT
• Central token credentials must be present
• signing key and signing password must both be present

Release publishing that includes Apple variants must also run on macOS. Use the macOS GitHub Actions workflow or a local macOS machine for public release publishing.

scripts/publish-central.ps1 still bridges .secrets into Gradle properties for validation tasks on Windows, but it intentionally blocks public snapshot and release publishing.

• If your consumer project reports artifacts such as lucide-core-iosarm64 or lucide-compose-iosarm64, first verify that your dependencies use the public coordinates lucide-icon-kmp and lucide-icon-kmp-compose.
• If you already use the public coordinates and iOS artifacts still fail to resolve, the current public snapshot was likely published without complete Apple variants.
• Republish the snapshot from macOS or the macOS CI workflow, then refresh dependencies in the consumer project.

Launch the Wasm browser sample with:

./gradlew :sample-compose:wasmJsBrowserDevelopmentRun

Build the production Wasm distribution with:

./gradlew :sample-compose:wasmJsBrowserDistribution

Desktop, Android, and iOS sample entry points also exist in sample-compose, but their execution depends on the corresponding local toolchains and host environment.

• Supports case-insensitive exact matching.
• Supports prefix matching.
• Supports substring matching.
• Supports tag-based matching.
• Supports localized picker labels for en and zh.
• Supports searching built-in icons in English and Chinese when locale is set accordingly.
• Shows all registered icons when the picker query is blank.
• Supports page-based pagination through pageSize.
• Applies searchLimit only when the picker query is not blank.

• Project source code is released under the MIT License. See LICENSE.
• Lucide Icons are licensed under the MIT License.
• The Lucide copyright notice is preserved in licenses/lucide-license.txt.
• See NOTICE for attribution details.