18. Packages without npm trauma
Registry-assigned versions, beskid pckg, lockfiles, and foreign libs: ecosystem without manual semver theatre.
Packages without npm trauma
Beskid packages are not “upload a folder, pick a version number that feels lucky, pray.” A .bpk artifact carries its exact version, and the Rust-backed pckg registry validates that immutable coordinate. Manifests declare dependencies; lockfiles make CI reproducible. If that sounds boring, good: we have enough trauma from ecosystems that treat breaking changes as personality.
Use the canonical Packages guide for credential, publication, consumption, and recovery procedures.
What you will find here
Section titled “What you will find here”| Section | Topic |
|---|---|
| pckg CLI | beskid pckg and the beskid_pckg crate. |
| Registry versions | Who assigns the version (hint: not your ego). |
| Publish first package | End-to-end publish walkthrough. |
| Foreign libraries | Linking native deps without npm cosplay. |
See also
Section titled “See also”- The pckg CLI: tutorial walkthrough of
beskid pckg - pckg command reference: full flag and subcommand reference
- Publish a package: verified procedure with expected results and recovery
- Doc and api.json: generated API docs ingested by pckg registry
- Package public surface: what registry consumers actually see
- Registry versions: who assigns the version
- Foreign libraries: linking native deps