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

@pull-up/cli

v0.0.3

Published

Collect scattered config files from your monorepo and generate them where your systems expect.

Readme

pull-up

Collect scattered config files from your monorepo and generate them where your systems expect.

The Problem

Many tools require config files in specific locations:

  • GitHub reads CODEOWNERS from .github/CODEOWNERS
  • GitHub Actions workflows must live in .github/workflows/
  • And more...

In a monorepo, each package has its own context. But these systems only look at root-level paths. You end up with a single massive file that every team has to edit, leading to merge conflicts and unclear ownership.

The Solution

pull-up lets you keep config files next to the code they describe, then collects and generates them to the locations your systems expect.

packages/
  core/
    CODEOWNERS        # * @core-team
  web/
    CODEOWNERS        # * @frontend-team
  api/
    CODEOWNERS        # * @backend-team

↓ pullup sync

.github/
  CODEOWNERS          # All entries merged with correct paths

Installation

npm install -D @pull-up/cli
# or
yarn add -D @pull-up/cli
# or
pnpm add -D @pull-up/cli

Configuration

Create a config file in your project root:

import { defineConfig, codeownersJob } from "@pull-up/cli";

export default defineConfig(codeownersJob());
// or export default defineConfig([codeownersJob()]);

Built-in Jobs

codeownersJob

Collects CODEOWNERS files from your monorepo and merges them into a single file.

codeownersJob({
  from: ["**/CODEOWNERS"], // default
  output: ".github/CODEOWNERS", // default
});

Custom Jobs

You can define custom jobs using defineJob:

import { defineConfig, defineJob } from "@pull-up/cli";

const myJob = defineJob({
  name: "my-job",
  from: ["packages/*/config.json"],
  output: "merged-config.json",
  transform: (sources, context) => {
    // sources: array of { path, contents }
    // context: { root, outputPath, existingContents }
    return JSON.stringify(sources.map((s) => JSON.parse(s.contents)));
  },
});

export default defineConfig([myJob()]);

Usage

Sync

Generate files from scattered sources:

pullup sync

Preview changes without writing:

pullup sync --dry-run

Check

Verify generated files are up to date (useful in CI):

pullup check

CLI Options

| Option | Description | | --------------- | ----------------------------------- | | --root <path> | Repository root path | | --cwd <path> | Working directory | | --dry-run | Preview without writing (sync only) |