16. Corelib: batteries with opinions
The standard library is injected, opinionated, and documented through api.json—not a grab bag of copy-pasted helpers.
Corelib: batteries with opinions
The corelib package is not “stdlib.zip you found on a forum.” The compiler injects it, the runtime backs part of it, and pckg serves the rest as normal, immutable package artifacts. Each .bpk carries its exact semver and registry dependency pins, while source .bproj files can keep workspace-local paths for development.
If you expected a monolithic System.IO graveyard, adjust expectations now.
What you will find here
Section titled “What you will find here”| Section | Topic |
| --- | --- |
| corelib command | Materialize the embedded template with beskid dev build corelib. |
| Injection and resolution | How every project gets the same canonical package. |
| Terminal and console | ANSI, streams, and why console is not syscall soup. |
| Doc and api.json | beskid dev syntax doc, structured API, and pckg docs UI. |
| Runtime-backed surfaces | What must call through the runtime vs pure Beskid. |
flowchart LR CLI[beskid CLI] --> inj[Corelib injection] inj --> src[beskid_corelib sources] src --> doc[beskid dev syntax doc / api.json] doc --> pckg[pckg registry docs] runtime[beskid_runtime] --> src