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

@deployagram/core

v1.0.0

Published

The framework-neutral part of the Deployagram test helpers: start or reuse the environment, post proxy configuration, and mark each test's end. Test framework adapters, such as @deployagram/vitest, build on it.

Readme

@deployagram/core

The part of the Deployagram test helpers that does not depend on a test framework:

  • starting, or finding, the Collector and the HTTP Proxy (@deployagram/environment)
  • posting the Proxy configuration (postProxyConfig)
  • marking the end of each test on the Collector, as <suite>.<test>
  • stopping only the containers the suite started

A test framework adapter wires these into its own hooks. @deployagram/vitest is one such adapter. The Jest, Mocha and node:test adapters are planned on the same core.

import { createDeployagramSuite } from '@deployagram/core';

const suite = createDeployagramSuite({
  name: 'ReceiveEmailTest',
  proxyConfig: { 'proxy.namesOfSourceApps.Emailer/email': 'EmailClient' },
});

beforeAll(() => suite.beforeAll());
beforeEach(() => suite.beforeEach());
afterEach(() => suite.afterEach(currentTestName));
afterAll(() => suite.stop());

The adapter supplies the hooks and the current test's name. The core does the rest.

Collector-only tests

For a test that stubs HTTP inside the test process, such as with MSW or Nock, there is no Proxy to configure. Start the environment with proxy: false, so no Proxy container is found or started:

const suite = createDeployagramSuite({
  name: 'MswSuite',
  environment: { proxy: false },
});

The suite then has no proxyUrl. Reading it is an error, and proxy configuration with proxy: false fails in beforeAll.