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

test-ecosystem-ci

v0.0.3

Published

Run CI across the ecosystem

Readme

ecosystem-ci

npm version npm downloads Unit Test

Run CI across the ecosystem

Install

npm i -D ecosystem-ci

Usage

  1. Create an ecosystem-ci.config.ts file at the root of your project. The config exports defineConfig and describes where your package lives, how to replace its dependency inside downstream repositories, and which actions to run in each ecosystem package.
import { defineConfig } from 'ecosystem-ci'

export default defineConfig({
  // required: name of the package to test in downstream repositories
  name: 'my-package',
  // optional: override the default '.' location
  packageLocation: './packages/my-package',
  // optional: override the default "file:../../packages/my-package" replacement
  npmImportReplacement: 'file:../../packages/my-package',
  // describe the ecosystem repositories to test against
  ecosystem: [
    {
      name: 'vite',
      repository: {
        github: {
          repo: 'vitejs/vite',
          branch: 'main',
        },
      },
      // optional: for pnpm monorepos, force my-package to be used when vite depends on it
      pnpmOverrides: {
        'vite@*>my-package': 'file:../../packages/my-package',
      },
      // optional: patch files before running actions
      patchFiles: {
        'package.json': (content) =>
          content.replace('workspace:*', 'file:../../packages/my-package'),
      },
      // actions to run in the cloned repository
      actions: [
        'pnpm install --no-frozen-lockfile',
        'pnpm run build',
        // you can also use a functions instead of string commands
        () => {},
        'pnpm run test-unit',
      ],
    },
  ],
})
  1. Run the CLI in the same directory to clone and test your ecosystem:
npx ecosystem-ci