vlt bugs

Usage:

Terminal

$ vlt bugs [<spec>] [--target=<query>]

Open bug tracker for a package in a web browser.

How It Works

The vlt bugs command locates and opens the bug tracker for any package in your dependency graph. It follows the following resolution strategy to find the best bug tracker URL:

1. Bugs field (string) – Uses the bugs property directly if it’s a string URL
2. Bugs field (object with url) – Uses bugs.url if available
3. Bugs field (object with email) – Creates a mailto: link if only email is provided
4. Repository Resolution – Falls back to the package’s repository field. For known git hosts (GitHub, GitLab, Bitbucket, etc.), generates the canonical issues URL
5. Fallback – If no bugs or repository info is found, falls back to the vlt.io package page

This means you always get taken to the most relevant bug tracker.

Basic Usage

Open bugs for current project

When run without arguments, vlt bugs reads your local package.json and opens the bug tracker for your current project:

Terminal

$ vlt bugs

This is particularly useful when working on a project and you want to quickly access your own issue tracker.

Open bugs for any package

Provide a package spec to open the bug tracker for any package, whether it’s installed in your project or not:

Terminal

# Open bugs for a specific package
$ vlt bugs express

# Open bugs for a specific version

$ vlt bugs [email protected]

# Open bugs for a scoped package

$ vlt bugs @vltpkg/graph

The command fetches the package manifest from the registry and determines the best bug tracker URL to open.

Query packages using —target

Use the --target option with DSS query syntax to find bug trackers for packages in your dependency graph:

Terminal

# Open bugs for a specific package in your graph
$ vlt bugs --target="#lodash"

# List bug tracker URLs for all direct dependencies

$ vlt bugs --target=":root > *"

# Find bugs for all packages from a specific scope

$ vlt bugs --target="[name^=@types]"

Note: When the query matches multiple packages, bug tracker URLs are listed instead of being opened automatically.

Use Cases

Reporting Issues

Quickly report bugs in dependencies:

Terminal

# Found a bug in a package? Report it
$ vlt bugs problematic-package

# Report issues for packages in your graph

$ vlt bugs --target="#problematic-package"

Checking for Known Issues

Before diving into debugging, check if others have reported the same issue:

Terminal

# Check issues for a troublesome dependency
$ vlt bugs --target="#failing-dep"

# Check issues for multiple packages

$ vlt bugs --target=":root > *"

Options

--target=<query>

Filter packages using DSS query syntax. When a single package matches, its bug tracker opens in your browser. When multiple packages match, their URLs are listed.

Terminal

# Open bugs for a single package
$ vlt bugs --target="#express"

# List bugs for all direct dependencies

$ vlt bugs --target=":root > *"

# List bugs for dev dependencies

$ vlt bugs --target=":type(dev)"