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

ducer

v0.0.6

Published

client agnostic data seeder library

Readme

Ducer - Framework-Agnostic Data Factory

Motivation

Ducer is a framework-agnostic library that allows you to generate data for your application in a way that closely mimics real-world conditions. Whether you're inserting data directly into a database, calling a REST API, or interacting with GraphQL, Ducer provides full flexibility—you define the data providers.

Instead of manually seeding your database or mocking API responses, Ducer encourages you to generate test data in the same way your application does. This ensures consistency and makes it easier to test complex scenarios.

Key Features

✅ Generate data that accurately reflects real-world conditions.
✅ Support for complex, interdependent data structures.
✅ Easily customize data at different levels of nesting.
✅ Retrieve all generated data, including dependencies, if needed.

Usage

1. Simple scenarios

const iMake: Ducer = new Ducer();
iMake.addFactory(
  "user",
  async (userData: Partial<UserInput>): Promise<User> => {
    return {
      ...{
        id: 123,
        firstName: "John",
        lastName: "Doe",
        createdAt: new Date("2022-02-02"),
      },
      ...userData,
    };
  }
);
const { user } = await iMake.user();
expect(user).toMatchObject({
  id: expect.any(Number),
  firstName: expect.any(String),
  lastName: expect.any(String),
  createdAt: expect.any(Date),
});

2. Complex scenarios

In more complex scenarios, we may need to create factories based on other factories. For example, we need to create an article that should have an author.

const iMake: Ducer = new Ducer();
iMake.addFactory(
  "user",
  (userData: Partial<UserInput>): User => {
    // write to DB/call API whatever you need
    return {
      ...{
        id: 123,
        firstName: "John",
        lastName: "Doe",
        createdAt: new Date("2022-02-02"),
      },
      ...userData,
    };
  }
);
iMake.addFactory(
  "article",
  (
    article: Partial<ArticleInput>,
    { author }: { author: User } // author will be automatically created
  ) => {
    return {
      id: 456,
      title: "Generated title",
      author_id: author.id,
    };
  },
  // we declare dependencies, where author is dependency name
  // and "user" is referenced to existing factory
  { author: "user" }
);
const { article, author } = await iMake.article(
  { title: "My article" },
  { author: { firstName: "Tome" } }
);
expect(article).toEqual({
  id: 456,
  title: "Generated title",
  author_id: 123,
});
expect(author).toMatchObject({
  id: 123,
  firstName: "Tome",
  lastName: "Doe",
});

3. Integration with data providers

Ducer allows you to integrate with any data provider, such as databases or APIs.
Here’s an example using Drizzle ORM to write directly to a database:


import {
  user as userTable,
} from '@/database/schema/drizzle.js';

const iMake: Ducer = new Ducer();
iMake.addFactory(
  "user",
  async (userData: Partial<UserInput>): Promise<User> => {
    const defaultData: UserInput = {
      id: uuidv4(),
      firstName: "John",
      lastName: "Doe",
      createdAt: new Date("2022-02-02"),
    }
    
    const result = {
      ...defaultData,
      ...data,
    };
    await database.insert(userTable).values(defaultData);

    return result;
  }
);

Why Use Ducer?

  • 🛠 Framework Agnostic: Works with any database, API, or service.
  • 🔄 Reproducible Data: Ensures consistent test data across environments.
  • 🔗 Supports Dependencies: Easily define complex object relationships.
  • ⚡ Customizable: Define your own factories and extend them as needed.