Repository navigation
Dependencies
github-actions[bot] edited this page Nov 4, 2026
·
2 revisions
source says where a dependency comes from. Everything except cmd is an NFB package. A field not listed for a source is an error.
source |
Required | Optional | Description |
|---|---|---|---|
cmd |
command |
name |
Runs the commands to install the dependency |
git |
url, ref
|
name, path
|
Package in a git repository |
url |
url |
name, sha256
|
Package manifest at a direct link |
local |
path |
name |
Package manifest on the filesystem |
store |
name, version
|
Package from the package store |
- Only direct dependencies are visible. If A depends on B and B depends on C, A does not see C's outputs or
[init]. - Each package builds against its own dependency versions.
- Two versions of the same package in one consumer is an error.
-
[build.env]is not inherited. A package only gets the environment it declares. -
source = "local"is rejected in packages fetched throughgit,urlorstore. - A
localpath can use../to reach folders outside the manifest's own. - A
gitpath must stay inside the repository, so../and absolute paths are errors. - A dependency must be a package. A project manifest cannot be used as one.
-
versionis required in a package. It does not have to matchref.