vlt / docs

    • PricingBenchmarks (opens in new window)Community (opens in new window)Feedback
  • Why vlt
  • Use cases
  • npm interoperability
  • Reference
Registry
  • Quick Start
  • Using Packages
  • Membership & Access
  • Dashboard
  • Authentication & Tokens
Client
  • Getting Started
  • Configuring
  • Authentication
  • Registries
  • Security
  • Workspaces
  • Affected
  • Catalogs
  • Peer Dependencies
  • Graph Modifiers
  • Global Installs
  • Report an issue

Share feedback

Got questions about how things work? Join our Discord.

Report an issue

  1. 1

    Check whether the issue already exists by searching our GitHub issue tracker. If you find a matching report, add a 👍 or a comment with your details instead of opening a duplicate.

  2. 2

    If nothing matches, open a new issue as a feature request or a bug report.

If the vlt CLI runs into an unexpected error, it writes the full details to an error-<pid>.log file and points you to the same tracker — attach that log to your bug report to help us reproduce it.

On this page

  • Report an issue
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