GIT-PKGS(1)

πŸ“¦
version 0.21.0 Β· 2 versions
, in nixpkgs unstable

πŸ’… NAME πŸ’…

ok so bestie, git-pkgs-resolve is the one that prints out your parsed dependency graph, straight from whatever local package manager you've got running. no cap, that's literally the whole job. πŸŽ€

✨ SYNOPSIS ✨

git-pkgs resolve [flags]

πŸ¦‹ DESCRIPTION πŸ¦‹

here's the vibe: it runs the dependency graph command of the package manager it detected, parses the output into a normalized dependency tree with PURLs, and then prints the result for you. slay. πŸ”₯

πŸ’€ heads up! this assumes your dependencies are already installed. if they're not, run git-pkgs install first, okay? don't come for me.

the examples, iconically:

git-pkgs resolve              # resolve dependencies (tree output)
git-pkgs resolve -f json      # output as JSON
git-pkgs resolve -e go        # only resolve Go ecosystem
git-pkgs resolve -m cargo     # force cargo
git-pkgs resolve --raw        # print raw manager output

🌸 OPTIONS 🌸

  • --dry-run[=false] β€” just shows you what would be run, without actually executing it. very "looking respectfully" energy. πŸ‘€
  • -e, --ecosystem="" β€” filters down to one specific ecosystem, if you're being picky.
  • -x, --extra=[] β€” extra arguments passed straight through to the package manager. costumize away, bestie.
  • -f, --format="text" β€” the output format. your choices are text and json. ✨
  • -h, --help[=false] β€” help for resolve. the classic.
  • -m, --manager="" β€” overrides the detected package manager. and yes, it takes precedence over -e, so that's the main character of the two. πŸ‘‘
  • --raw[=false] β€” prints the raw manager output instead of parsed JSON. unfiltered, no edits, raw footage. 🎬
  • -t, --timeout=5m0s β€” the timeout for the resolve operation. default is 5m0s, so it will wait, but not forever. πŸ’€

🌈 OPTIONS INHERITED FROM PARENT COMMANDS 🌈

  • --color="auto" β€” when to colorize output: auto, always, never. aesthetic choices, honestly. 🎨
  • --include-submodules[=false] β€” includes git submodules when scanning for manifests. yes, even those. 🫢
  • -p, --pager[=false] β€” use a pager for the output, so it doesn't just scroll past you at the speed of light.
  • -q, --quiet[=false] β€” suppresses non-essential output. for the girlies who want the silent-luxury terminal experience. 🀫

πŸ’œ SEE ALSO πŸ’œ

  • git-pkgs(1) β€” the parent, the icon, the moment. πŸŽ€

⭐ HISTORY ⭐

  • 28-Oct-2026 β€” auto generated by spf13/cobra. not me, not you, the machines did this one. 😭

okay that's the whole page, bestie β€” go resolve those deps and slay βœ¨πŸ’…

git-pkgs Β· Oct 2026 Β· written by the Git Pkgs crew, delivered with love πŸ«ΆπŸ¦‹

πŸ“¦ where this page comes from