asok-lucide
Lucide Icons integration for the Asok Framework.
Render beautiful Lucide Icons server-side with zero client-side JavaScript overhead.
Resources
- PyPI Project: pypi.org/project/asok-lucide
- Asok Framework: asok-framework.com
- Asok Repository: github.com/asok-framework/asok
- Lucide Icons: lucide.dev
Installation
pip install asok-lucide
For development or contributing, install in editable mode:
pip install -e .
Setup
Register the extension in your app.py:
from asok import Asok
from asok_lucide import AsokLucideExtension
app = Asok()
app.register_extension(AsokLucideExtension)
You can optionally configure a custom alias (e.g. icon) to shorten the template helper name:
app.register_extension(AsokLucideExtension(alias="icon"))
Usage
Direct template helper
<button>
{{ lucide("shopping-cart", class_="w-5 h-5 text-white") }}
<span>Add to Cart</span>
</button>
Or using the custom alias (if registered):
{{ icon("user", class_="w-6 h-6") }}
Template filter
{{ "home" | lucide(class_="w-6 h-6", stroke_width="1.5") }}
All standard attributes (such as class, stroke-width, stroke, fill, style) can be customized dynamically. Use class_ or snake_case stroke_width in template helpers.
Development & Publishing
Updating the Icon Dataset
The icons are pre-compiled and bundled inside the package (asok_lucide/data/lucide-icons.json) to guarantee fast, deterministic server-side rendering without runtime network dependencies.
To update the bundled Lucide Icons (e.g., when a new Lucide version releases):
- Run the update script to fetch and resolve all icon definitions & aliases from Iconify:
python scripts/fetch_icons.py - Run the test suite to verify everything still renders correctly:
python -m pytest tests
- Commit the updated
lucide-icons.jsonto Git.
Releases & GitHub Actions
A GitHub Actions workflow is configured in .github/workflows/release.yml. When you publish a release on GitHub:
- The workflow checks out the repository (which contains the committed
lucide-icons.jsondata). - It builds the wheel and source distributions.
- It automatically publishes the package to PyPI using PyPI's Trusted Publishing OIDC integration.
Metadata
Release files for asok-lucide 1.0.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| asok_lucide-1.0.1.tar.gz | 90.6 kB | With provenance | Details for asok_lucide-1.0.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| asok_lucide-1.0.1-py3-none-any.whl | Python 3 | none | any | Details for asok_lucide-1.0.1-py3-none-any.whl |
Total release size: 179.8 kB
Release files / asok_lucide-1.0.1.tar.gz
| Download URL | asok_lucide-1.0.1.tar.gz |
|---|---|
| Size | 90.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f22b70fdb1dd8e35ea3e52976e4a05cbe396606acc295bc72ff92c3762ae1a0f
|
|
BLAKE2b-256 checksum How to use checksums |
9f43a98488e3fcfa4b37d0ec3c03a240a9af6ccaeb84261936318b5c6fb33714
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 7, 2026.
Transparency logRelease files / asok_lucide-1.0.1-py3-none-any.whl
| Download URL | asok_lucide-1.0.1-py3-none-any.whl |
|---|---|
| Size | 89.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
77c7415db5227580e0d2605a5627758c2821c6deaaf6d8c060e2596c0fc3db4e
|
|
BLAKE2b-256 checksum How to use checksums |
e2514af3c09df2a6c6418c71ae861e589fce3e180c5a2b4ec48fb09ce9828bd7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 7, 2026.
Transparency logSecurity for asok-lucide 1.0.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for asok_lucide-1.0.1.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 7, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.