03. Project.proj or it didn't happen
Manifests, targets, dependencies, lockfiles, and the resolver graph that actually builds.
Project.proj or it didn't happen
Every serious Beskid program anchors on Project.proj at the project root—not a twelve-page YAML poem, not a solution file with six nested repos and a prayer.
This chapter is the mental model for what you are building (targets), what you depend on (dependencies), and how tooling orders work before codegen.
What you will find here
Section titled “What you will find here”| Section | Topic |
|---|---|
| Project manifest | project, target, dependency blocks. |
| Targets and outputs | App, Lib, Test, entries, artifacts. |
beskid new | Scaffolding templates without hand-copy hell. |
| Fetch, lock, update | Resolution, Project.lock, reproducibility. |
| Tree and resolution | DAG order, obj/beskid, debugging graphs. |
By the end of this chapter
Section titled “By the end of this chapter”- Read a minimal
Project.projwithout panic. - Predict build order for dependencies.
- Know when
Project.lockshould change and why.