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/app

v0.8.1

Published

The primary typed application-authoring API for RELKIT.

Readme

@relkit/app

@relkit/app is the public entry point for application configuration and descriptors. Provider implementations live in independently installable integration packages.

import "@relkit/pulumi";
import { defineApp, defineEnv, env as binding } from "@relkit/app/config";
import { aws } from "@relkit/aws";
import { docker } from "@relkit/docker";
import { redis } from "@relkit/redis";
import { s3 } from "@relkit/s3";

export default defineApp({
  env: defineEnv({}),
  cache: {
    requests: docker(redis({ url: binding.secret("REQUESTS_REDIS_URL") })),
    timeline: aws(redis(), { engine: "valkey" }),
  },
  bucket: { receipts: aws(s3(), { versioning: true }) },
  defaults: { cache: "requests", bucket: "receipts" },
  deployment: { engine: "pulumi", host: "aws" },
  server: { port: 3000 },
  inspector: { enabled: true },
});

Direct adapters describe connected services. docker(adapter) adds a local development recipe, and aws(adapter) makes AWS own that resource in deployment. Named binding values are private to their provider binding and do not become handler-visible ctx.env fields.

Cloud and deployment default to none. Tests provide replacements explicitly by capability and profile; environment names never swap providers.

Inspection defaults to disabled. inspector.enabled selects a development bridge; inspector.connection optionally sets its bind host and port (defaults 127.0.0.1:0). The standalone tool owns UI port 3210. The obsolete inspector.port and inspector.enabledInProduction settings are rejected. Installing or running the standalone tool is separate from application configuration.