openchar-frontend
Prebuilt Inline Studio web UI (SPA), packaged so Inline Core can serve it on a single port -
mirroring ComfyUI's comfyui-frontend-package. End users pip install openchar-core (which depends on
this), then run python main.py; no Node build on their machine.
What's in the wheel
The payload is the built SPA under openchar_frontend/static/ (index.html + hashed assets/).
Core resolves this dir via inline_core.server.frontend.resolve_frontend_root and mounts it.
Publishing (release only)
# in the Inline Studio repo
npm run build:spa # -> dist-web/
cp -r dist-web/* packages/frontend/openchar_frontend/static/
cd packages/frontend
python -m build && twine upload dist/* # publish to PyPI
Local development - don't republish
Point Core at a local build instead:
npm run build:spa
python main.py --front-end-root ../Inline-Studio/dist-web # in the Inline Core repo
# or, for HMR:
npm run dev:web # Vite dev server on :5173, proxying the backend to Core
1 maintainer
Metadata
1 maintainer
Release files for openchar-frontend 1.3.17
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 | |
|---|---|---|---|---|
| openchar_frontend-1.3.17.tar.gz | 3.3 MB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| openchar_frontend-1.3.17-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 6.7 MB
Release files / openchar_frontend-1.3.17.tar.gz
| Download URL | openchar_frontend-1.3.17.tar.gz |
|---|---|
| Size | 3.3 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e2c98002dee4a05477a9ad8a007f8c1100b7c61d7b1884bca04ae1500110ca59
|
|
BLAKE2b-256 checksum How to use checksums |
2c96b71e6392a3b23300a92209b0286e53ca706a4a6f276a34ebd1e877bcff70
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Sep 7, 2026.
Transparency logRelease files / openchar_frontend-1.3.17-py3-none-any.whl
| Download URL | openchar_frontend-1.3.17-py3-none-any.whl |
|---|---|
| Size | 3.3 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
17cbd833fe761bec11f98419702110ab0315cd640c500165efc5decbb6987e59
|
|
BLAKE2b-256 checksum How to use checksums |
79aa2b4ccbecf8269d3925f2b699716f896f42514677c2e37db3be7ad3823b5d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Sep 7, 2026.
Transparency logSecurity for openchar-frontend 1.3.17
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 openchar_frontend-1.3.17.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 Sep 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.
