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

@edd-kernel/factory

v0.2.0-alpha.1

Published

Factory for creating EDD Kernel clients from provider names.

Readme

@edd-kernel/factory

Factory for creating EDD Kernel clients from provider names.

This package belongs to the EDD Kernel composition layer. It owns provider name resolution and dynamic provider loading. It does not own provider-specific transport behavior; that belongs to each @edd-kernel/provider-* package.

Repository: brunnofoggia/edd-kernel-js

Install

This is the package an application imports from. Install it with the provider your application uses:

npm install @edd-kernel/factory @edd-kernel/provider-aws-sqs

It re-exports the whole of @edd-kernel/contracts — the types, the enums, the error classes and the provider registry — so the application does not install the contract separately.

Provider packages are optional peer dependencies. Install only the provider package used by the application.

Usage

import { EddProviderName, createEddClient } from '@edd-kernel/factory';

const client = await createEddClient({
    providerName: EddProviderName.AwsSqs,
    createIfNotExists: true,
    options: {
        region: 'us-east-1',
    },
});

await client.send({ queueName: 'email-jobs' }, { type: 'email.requested', payload: {} });

Use options for provider-specific configuration. Shared EDD Kernel options stay at the top level:

const client = await createEddClient({
    providerName: EddProviderName.RabbitMq,
    createIfNotExists: true,
    autoAck: false,
    concurrency: 4,
    options: {
        url: 'amqp://guest:guest@localhost:5672',
    },
});

providerName is always required. To use an application-defined provider, pass its class constructor in providerClass:

import { createEddClient } from '@edd-kernel/factory';
import { InMemoryEddClient } from '@edd-kernel/provider-in-memory';

class CustomEddClient extends InMemoryEddClient {
    static readonly providerName = 'custom';
}

const client = await createEddClient({
    providerName: CustomEddClient.providerName,
    providerClass: CustomEddClient,
    createIfNotExists: true,
});

providerClass must be a class to instantiate, not an existing client instance. If the class declares a static providerName, it must match the configured name. Custom names are accepted only when providerClass is provided; otherwise the name must identify a built-in provider.

Providers

Supported provider names:

| Name | Package | | ------------- | ---------------------------------- | | in-memory | @edd-kernel/provider-in-memory | | aws-sqs | @edd-kernel/provider-aws-sqs | | rabbitmq | @edd-kernel/provider-rabbitmq | | gcp-pub-sub | @edd-kernel/provider-gcp-pub-sub |

The same options are exported as EddProviderName. Provider package and class targets are exported as EDD_PROVIDER_TARGET_BY_NAME; the package-only mapping remains available as EDD_PROVIDER_PACKAGE_BY_NAME.

Common Options

The factory forwards shared EDD Kernel options to the selected provider:

  • serialization
  • autoIdempotencyKey
  • createIfNotExists
  • autoAck
  • unhandledErrorAction
  • concurrency
  • logger
  • debug