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

@rawdash/connectors

v0.29.2

Published

Aggregate package bundling every built-in Rawdash connector. Depend on this one package instead of N individual @rawdash/connector-* packages.

Readme

@rawdash/connectors

npm version license

Aggregate package that bundles every built-in Rawdash connector. Depend on this one package instead of listing each @rawdash/connector-* package individually — adding a connector to the monorepo flows into the aggregate automatically, with no consumer-side changes and no version drift.

The contents are generated at build time from the connector packages by scripts/generate-connectors-package.ts.

Install

npm install @rawdash/connectors

Entry points

The package has two subpath exports, deliberately split so a metadata-only consumer never bundles connector sync logic:

@rawdash/connectors/metadata

Metadata only — the display, configuration, and cost descriptors a catalog needs, never the runnable connector class. Combined with sideEffects: false, a bundler tree-shakes the connector class bodies out of a metadata-only build.

import {
  connectorMetadata,
  connectorMetadataById,
} from '@rawdash/connectors/metadata';

for (const c of connectorMetadata) {
  console.log(c.id, c.doc.displayName);
}

const github = connectorMetadataById['github-actions'];

Each entry exposes id, packageName, doc, configFields, resources, and (where the connector declares one) cost.

@rawdash/connectors/registry

The runnable connector classes, behind per-connector lazy loaders. The dynamic import() per connector preserves the lazy-load boundary: resolving one connector never pulls the others' class or sync code into the same chunk.

import {
  connectorIds,
  connectorLoaders,
  loadConnector,
} from '@rawdash/connectors/registry';

const GitHubConnector = await loadConnector('github-actions');

License

Apache-2.0