GIT-PKGS(1)

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

πŸ’… GIT-PKGS(1) β€” the Git Pkgs Manual, bestie edition πŸŽ€

okay so this is git-pkgs(1), from the Git Pkgs Manual, and today we're doing the browse subcommand. it's lowkey the most useful little thing ever. let's go πŸ¦‹


✨ NAME ✨

git-pkgs-browse β€” open an installed package's source in your editor. that's it, that's the whole vibe 🫢


🌸 SYNOPSIS 🌸

git-pkgs browse  [flags]

(no cap, that's the entire invocation. flags optional, slaying mandatory πŸ’…)


πŸ”₯ DESCRIPTION πŸ”₯

Open the source code of an installed package in your editor. literally just look at the code, bestie, it's right there ✨

So here's the magic: it detects the package manager from lockfiles in the current directory, finds where the package is actually installed, and opens it in $EDITOR. iconic behaviour, no notes πŸ‘‘

Examples:

git-pkgs browse lodash           # open in $EDITOR
git-pkgs browse lodash --path    # just print the path
git-pkgs browse lodash --open    # open in file browser
git-pkgs browse lodash -e npm    # specify ecosystem
git-pkgs browse serde -m cargo   # specify manager

see how easy that was?? main character energy fr fr πŸ’œ


πŸŽ€ OPTIONS πŸŽ€

  • -e, --ecosystem="" β€” filter it down to one specific ecosystem, if you're being picky 🌈
  • -h, --help[=false] β€” help for browse. the classic. the goat. press it when confused πŸ™ˆ
  • -m, --manager="" β€” override the detected package manager, for when the auto-detect is being a little silly and you know better πŸ’€
  • --open[=false] β€” open in file browser instead of editor. different vibe, same package πŸ“
  • --path[=false] β€” just print the path instead of opening the editor. dry run, but make it fashion ✨
  • -t, --timeout=30s β€” timeout for path lookup. default is 30s, so if it's taking forever, that's on the search, not on you 😭

🧚 OPTIONS INHERITED FROM PARENT COMMANDS 🧚

these bad boys come from the parent command β€” you didn't ask, but you're getting them anyway πŸ’–

  • --color="auto" β€” when to colorize output: auto, always, never. pick your aesthetic 🌸
  • --include-submodules[=false] β€” include git submodules when scanning for manifests. yes, those submodules 🫠
  • -p, --pager[=false] β€” use pager for output. scroll responsibly πŸ’…
  • -q, --quiet[=false] β€” suppress non-essential output. for when you want peace and quiet 🀫

⭐ SEE ALSO ⭐

  • git-pkgs(1) β€” go see the parent, it misses you πŸ₯Ί

πŸ“œ HISTORY πŸ“œ

28-Oct-2026 β€” auto generated by spf13/cobra. not a human, a robot, and honestly it ate πŸ€–βœ¨


ok that's the whole page!! go browse some packages, bestie, you've earned it πŸ’œπŸ¦‹

sign-off time πŸŽ€ β€” this page came from git-pkgs, dated Oct 2026, filed under GIT-PKGS(1) in the manuals. mwah, bye bestie!! πŸ’–

πŸ“¦ where this page comes from