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

@digta/config

v0.1.0

Published

Tiny config manager: load / save / watch JSON, YAML, and .env files with one API.

Readme

@digta/config

Tiny config manager for Node. One API to load / save / watch — format picked automatically from the file extension: JSON, YAML, or .env.

npm install @digta/config

Usage

import createConfig from "@digta/config";
// or: const createConfig = require("@digta/config");

const config = createConfig("./config.yaml", {
  defaults: { port: 3000, host: "localhost" },
});

config.load();              // read + parse the file into config.data
console.log(config.data);   // { port: 3000, host: "localhost", ... }

config.data.port = 8080;    // mutate directly
config.save();              // write back in the same format

const stop = config.watch((data) => {
  console.log("config changed:", data);
});
// stop();                  // call to stop watching

Formats

Chosen by extension — no config needed:

| File | Format | Notes | |-----------------|--------|----------------------------------------------| | *.json | JSON | Full nesting, typed values | | *.yaml *.yml| YAML | Full nesting; requires js-yaml (installed) | | *.env .env | dotenv | Flat KEY=VALUE, string values only |

.env values are always strings (that's what env vars are). Use JSON or YAML if you need nested objects or numbers/booleans.

API

createConfig(filePath, { defaults? }) → a config object:

| Member | Description | |-----------------|--------------------------------------------------------------------| | .data | The parsed object. Read and mutate it directly. | | .load() | Parse the file into .data. A missing file keeps defaults. | | .save() | Serialize .data back to the file in its format. | | .watch(cb) | Reload on change, call cb(data). Returns an unwatch() function. | | .path | The file path. | | .format | "json" | "yaml" | "env". |

defaults are merged shallowly under loaded values (loaded keys win). Missing file → .data stays as the defaults.

License

MIT