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

dipend-graph

v1.0.2

Published

A library for generating a DAG (Directed Acyclic Graph) of dependencies registered in Dipend's dependency container.

Downloads

47

Readme

Issues Apache-2.0 License Contributors

Features

  • Interface-based Dependency Injection: Use TypeScript interfaces as references for dependencies, ensuring strong type safety.
  • Mapped Dependencies: Register and resolve multiple implementations of the same interface by key. This allows you to map different behaviors or strategies to specific identifiers and retrieve them dynamically at runtime based on context.
  • Singleton and Transient Support: Easily configure lifetime scopes for your services.
  • Minimal Setup: Get started quickly with a simple CLI.
  • Easy to Extend: Open and flexible architecture.

Getting Started

Installation

First, initialize Dipend in your project:

npx dipend init

This command will:

  • Add Dipend and ts-patch to your package.json
  • Update your tsconfig.json with necessary configuration
  • Prepare your project for dependency injection

Then install dependencies:

npm install

Basic Usage

Here’s a simple example to show how Dipend works:

import { DependencyContainer } from "dipend";

// Define an interface
interface ILogger {
  info(message: string): void;
}

// Implement the interface
class Logger implements ILogger {
  public info(message: string) {
    console.info(`INFO: ${message}`);
  }
}

// Create a dependent class
class Greeter {
  constructor(private logger: ILogger) {}

  public greet(name: string): string {
    const message = `Hello, ${name}!`;
    this.logger.info(message);
    return message;
  }
}

// Create the container
const dependencyContainer = new DependencyContainer();

// Register dependencies
dependencyContainer.addSingleton<ILogger, Logger>();
dependencyContainer.addTransient<Greeter>();

// Build singletons (optional if you want them ready immediately)
dependencyContainer.buildSingletons();

// Resolve and use a dependency
const greeter = dependencyContainer.getDependency<Greeter>();
const result = greeter.greet("World");
console.log(result);

More Examples

Looking for more use cases or advanced configurations?
Check out the full documentation.

Why Dipend?

While many dependency injection libraries exist, Dipend is the only one (as of now) that fully supports using interfaces as references for dependency resolution without needing extra boilerplate or manual token management.

This means you can register and retrieve implementations by their interfaces directly, preserving clean principles while keeping your code strongly typed and maintainable.

Contributing

Contributions make the open-source community such an amazing place to learn, inspire, and create. We warmly welcome your contributions!

Before contributing, please read the following:

If you like the project, don't forget to give it a ⭐️!

License

Copyright 2025 Saulo V. Alvarenga. All rights reserved.

Licensed under the Apache License, Version 2.0.

See LICENSE for complete license information.