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

@outfitter/stack

v0.1.0-rc.1

Published

Version coordination meta-package for Outfitter

Readme

@outfitter/stack

Version coordination meta-package for Outfitter.

Purpose

This package ensures compatible versions across all @outfitter/* packages. Install it alongside specific packages to get coordinated version constraints via peerDependencies.

Installation

bun add @outfitter/stack

When to Use

Use @outfitter/stack when:

  1. Building applications that use multiple Outfitter packages
  2. Ensuring compatibility between package versions
  3. Checking version requirements programmatically
# Install stack alongside the packages you need
bun add @outfitter/stack @outfitter/cli @outfitter/logging @outfitter/config

The stack's peerDependencies will warn if you have incompatible versions installed.

Version Matrix

See VERSIONS.md for the complete compatibility matrix.

Current Release (0.1.0-rc.1)

| Package | Minimum Version | |---------|-----------------| | @outfitter/agents | 0.1.0-rc.1 | | @outfitter/contracts | 0.1.0-rc.1 | | @outfitter/types | 0.1.0-rc.1 | | @outfitter/cli | 0.1.0-rc.1 | | @outfitter/config | 0.1.0-rc.1 | | @outfitter/logging | 0.1.0-rc.1 | | @outfitter/file-ops | 0.1.0-rc.1 | | @outfitter/state | 0.1.0-rc.1 | | @outfitter/ui | 0.1.0-rc.1 | | @outfitter/mcp | 0.1.0-rc.1 | | @outfitter/index | 0.1.0-rc.1 | | @outfitter/daemon | 0.1.0-rc.1 | | @outfitter/testing | 0.1.0-rc.1 |

Exports

STACK_VERSION

The current stack version (matches package.json).

import { STACK_VERSION } from "@outfitter/stack";

console.log(`Using Outfitter Stack ${STACK_VERSION}`);

MINIMUM_VERSIONS

Minimum compatible versions for each package.

import { MINIMUM_VERSIONS } from "@outfitter/stack";

// Check if a package meets the minimum version
const cliMinimum = MINIMUM_VERSIONS["@outfitter/cli"]; // "0.1.0-rc.0"

OutfitterPackage

Type for valid package names in the stack.

import { type OutfitterPackage, MINIMUM_VERSIONS } from "@outfitter/stack";

function getMinVersion(pkg: OutfitterPackage): string {
  return MINIMUM_VERSIONS[pkg];
}

getMinVersion("@outfitter/cli"); // "0.1.0-rc.0"
getMinVersion("@outfitter/invalid"); // TypeScript error

API Reference

| Export | Type | Description | |--------|------|-------------| | STACK_VERSION | string | Current stack version | | MINIMUM_VERSIONS | Record<OutfitterPackage, string> | Minimum versions for all packages | | OutfitterPackage | type | Union type of valid package names |

Dependency Tiers

Packages are organized into tiers based on stability:

Foundation (cold)

Stable APIs, rarely change:

  • @outfitter/contracts - Result/Error patterns
  • @outfitter/types - Branded types

Runtime (warm)

Expected to evolve:

  • @outfitter/cli - CLI framework
  • @outfitter/config - Configuration
  • @outfitter/logging - Structured logging
  • @outfitter/file-ops - File operations
  • @outfitter/state - State management
  • @outfitter/ui - Terminal UI
  • @outfitter/mcp - MCP server framework
  • @outfitter/index - SQLite FTS5 indexing
  • @outfitter/daemon - Daemon lifecycle

Tooling (lukewarm)

Workflow-focused:

  • @outfitter/testing - Test harnesses

Related Packages

All @outfitter/* packages are designed to work together. See individual package documentation:

License

MIT