Publish your first package

Informative guide. This Book page explains Beskid but does not define the standard. For normative requirements, use the Beskid Standard.

The step-by-step guide with commands and role requirements lives in the reference tree—this section exists so the tutorial nav has a landing page that does not duplicate every flag.

Read this next

Publish a package — protect the API key, create the package record, pack, inspect, upload, and verify the immutable version.

Before you publish

• Run beskid doc so .beskid/docs/api.json exists for pckg registry docs ingestion.
• Run tests (beskid test) if your package is more than a manifest cosplay.
• Confirm public API boundaries — see Package public surface: registry consumers import what you exported, not what you “meant.”

See also

• pckg command reference — full subcommand and flag reference
• The pckg CLI — tutorial walkthrough
• Doc and api.json — generated API docs ingested by pckg registry
• Packages without npm trauma — chapter overview