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

@codelia/config

v0.1.64

Published

Config schema + registry (no I/O).

Readme

@codelia/config

Config schema + registry (no I/O).

This package does not read files or environment variables. It only provides:

  • Config types
  • A registry for defaults
  • Merge/resolve of loaded config layers

File I/O lives in @codelia/config-loader.

Minimal config.json

{
  "version": 1,
  "model": {
    "provider": "openai",
    "name": "gpt-5.2-codex",
    "reasoning": "medium",
    "verbosity": "medium"
  },
  "permissions": {
    "allow": [
      { "tool": "read" },
      { "tool": "skill_load", "skill_name": "repo-review" }
    ],
    "deny": [{ "tool": "bash", "command": "rm" }]
  }
}

How it is used (runtime/CLI)

  1. Modules register defaults into the shared registry.
  2. CLI/runtime loads the config file.
  3. CLI/runtime merges defaults + config and uses the effective values.
import { configRegistry } from "@codelia/config";
import { loadConfig } from "@codelia/config-loader";

// defaults are registered by modules (e.g. @codelia/core on import)
const config = await loadConfig("/path/to/config.json");
const effective = configRegistry.resolve([config]);

Where config.json is loaded

Current behavior (runtime/CLI integration path):

  • Global config + project config are both supported.
  • Global config path is resolved in runtime/CLI.
  • CODELIA_CONFIG_PATH overrides the global config file location.
  • Project config is loaded from .codelia/config.json under the working directory.
  • Effective config is resolved by merging defaults + global + project (project wins on conflicts).

See dev-docs/specs/storage-layout.md for the default global path (home/XDG).