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

@relkit/config

v0.7.12

Published

RELKIT environment configuration API; prefer @relkit/app/config in applications.

Downloads

3,585

Readme

@relkit/config

@relkit/config declares typed environment rules and safe metadata. Declaration modules are value-free: importing one creates builders and metadata but does not read process, file, or runtime environment values.

Declare environment rules

import { defineEnv, env } from "@relkit/app/config";

export default defineEnv({
  APP_MODE: env.literal("development", "test", "production").default("development"),
  WORKER_PORT: env.port().default(3210),
  API_URL: env.url().requiredIn("production"),
  API_TOKEN: env.secret().optional().description("Token for the external API"),
});

The declaration above records parsing rules, requirements, defaults, and sensitivity. It does not resolve a value at module import time. Keep runtime resolution in an explicit startup function with an explicit source:

import { projectEnv, resolveEnv } from "@relkit/app/config";
import definition from "./env";

export const environmentMetadata = projectEnv(definition);

export function resolveRuntimeEnv(
  source: Readonly<Record<string, string | undefined>>,
  environment: string,
) {
  return resolveEnv(definition, { environment, source });
}

export function start(source: Readonly<Record<string, string | undefined>>, environment: string) {
  return resolveRuntimeEnv(source, environment);
}

projectEnv is safe for graph and inspector metadata: it includes names, types, requirements, default presence, and sensitivity without resolved values or secret defaults. resolveEnv returns an immutable value object and reports missing or malformed values with structured issues.

Effect operations

The synchronous functions above run their Effect implementations. Applications that already use Effect can call defineEnvEffect, projectEnvEffect, and resolveEnvEffect directly with an explicit source and environment name.

Expected failures have stable ConfigValidationError or EnvResolutionError tags, so an Effect caller can recover with Effect.catchTag. Operations emit config.* spans and bounded call, failure, and duration metrics by default. Provide ConfigTelemetry as a Layer when a different observer is needed.

Run this package's behavior suite with bun run --cwd packages/config test or its enforced coverage gate with bun run --cwd packages/config test:coverage.

PORT is reserved for framework server selection and is rejected by defineEnv; configure it with server.port, the PORT process variable, or the CLI --port flag.