Blyx Nest Blyx language
Registry / Publish

Publish to Blyx Nest

Submit a versioned Blyx library or framework, or propose a tool built specifically for Blyx.

Prepare your release

Commit a Blyx.toml manifest, a public .blyx module and its license to your source repository. Give the release a stable X.Y.Z version. Supply a runnable main.blyx that imports the module from vendor and an expected.txt containing its exact output.

Submit a package

Fork the registry and clone your fork. From that checkout, use Python 3.11 or newer to prepare the archive and release record. Replace the paths, tag, module and project details with your own.

python registry/submit.py ../my-package --ref v0.1.0 --repository https://github.com/OWNER/REPO --kind library --title MyPackage --description "Describe the task it solves" --module mypackage --license MIT --example ../demo/main.blyx --expected ../demo/expected.txt

Commit the new files under entries/ and archives/ and open a pull request. Registry checks validate the manifest, module, license, archive paths and checksum. A maintainer verifies the source ownership and example before merging. Merged releases are deployed automatically. Existing versions are immutable.

List a developer tool

For a compiler, package client or another tool specific to Blyx, include its source repository, versioned downloads, license, install guide and a command that demonstrates its Blyx integration.