vlt / docs

  • PricingBenchmarks (opens in new window)Community (opens in new window)Feedback
  • Overview
  • bugs
  • build
  • cache
  • ci
  • config
  • create
  • docs
  • exec-cache
  • exec-local
  • exec
  • help
  • init
  • install
  • list
  • login
  • logout
  • outdated
  • pack
  • ping
  • pkg
  • publish
  • query
  • registry
  • repo
  • run-exec
  • run
  • setup
  • token
  • uninstall
  • version
  • view
  • whoami
  • Local package
  • Fields
  • Options
  • --view=<human | json>
  1. Client
  2. /
  3. Commands
  4. /
  5. view

vlt view

Usage:

Terminal
$ vlt view <pkg>[@<version>] [<field>]
$ vlt view <pkg>[@<version>] [--view=human | json]

View registry information about a package: manifest of the resolved version, dist-tags, maintainers, versions and, when available, vlt security scores and alerts.

Aliases: info, show.

Local package

. views the package in the current directory (nearest package.json, walking up). Running vlt view with no arguments does the same.

Terminal
$ vlt view .
$ vlt view .@1.2.3
$ vlt view . version
  • . looks up the local package name in the configured registry (default dist-tag); .@<version> picks a version or tag.
  • Private packages ("private": true) are never looked up in the registry; their local package.json info is shown instead.
  • Path specs (./pkg, file:pkg) show that directory's package.json, relative to the project root.

Fields

Pass a field to print only its value. Nested fields use dot-prop syntax:

Terminal
$ vlt view express dist-tags.latest
$ vlt view express dependencies.debug

Options

--view=<human | json>

Output format. Defaults to human, or json when not a tty.


PreviousversionNextwhoami

On this page

  • Local package
  • Fields
  • Options
  • --view=<human | json>
Edit this page

Deploy your package on vlt.io

Publish scoped and private packages, manage organizations and access, and give every developer and CI environment a consistent source for public and private JavaScript dependencies.

Publish now