npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@vltpkg/config

v1.0.0-rc.18

Published

Project config logic for vltpkg

Readme

@vltpkg/config

Config utilities for the vlt client.

Usage · API

Overview

These are config utilities used by the vlt cli.

Usage

import { get, set, edit, list, del } from '@vltpkg/config'

// Assuming you have a LoadedConfig instance from @vltpkg/cli-sdk
// const conf = await loadConfig()

// Get a config value by key
const colorValue = await get(conf) // requires conf.positionals[1] to be the key name
// Supports dot notation for nested properties in record fields
// e.g., conf.positionals = ['get', 'registry.npmjs.org']

// Set config values using key=value pairs
// conf.positionals should contain pairs like ['set', 'color=auto', 'timeout=5000']
await set(conf)
// Creates config file if it doesn't exist when called with no pairs
// Supports dot notation for record fields: 'registry.npmjs.org=https://registry.npmjs.org/'

// Edit the config file with the configured editor
await edit(conf) // opens conf.get('config') file in conf.get('editor')

// List all current config values as key=value pairs
const allConfig = list(conf) // returns array of 'key=value' strings

// Delete config keys
// conf.positionals should contain keys to delete: ['del', 'color', 'timeout']
await del(conf) // removes specified keys from conf.get('config') file

API

get(conf: LoadedConfig)

  • Retrieves a single config value by key
  • Supports dot notation for accessing nested properties in record fields
  • Returns the value as string | number | boolean | string[] | Record<string, string> | undefined
  • Requires exactly one key in conf.positionals[1]

set(conf: LoadedConfig)

  • Sets config values from key=value pairs in conf.positionals
  • Creates an empty config file if no pairs are provided
  • Supports dot notation for record fields (e.g., registry.npmjs.org=value)
  • Writes to the config file specified by conf.get('config')

edit(conf: LoadedConfig)

  • Opens the config file in the editor specified by conf.get('editor')
  • Uses spawnSync to launch the editor with the config file path
  • Throws an error if the editor command fails

list(conf: LoadedConfig)

  • Returns all current config options as an array of 'key=value' strings
  • Converts the internal config records to a flat list format

del(conf: LoadedConfig)

  • Deletes specified config keys from the config file
  • Requires at least one key in conf.positionals (after the command name)
  • Removes keys from the file specified by conf.get('config')