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 🙏

© 2024 – Pkg Stats / Ryan Hefner

@declaro/di

v2.0.0-beta.13

Published

Dependency injection with excellent type introspection

Downloads

126

Readme

Declaro Dependency Injection

Manage your application's dependencies in a declarative and typesafe fashion.

Values

  1. Reduce human error factors. We shouldn't have to coerce types or rely on developers to remember which dependencies can map to which args.
  2. First-class typing. Everything should be type introspected. Yes, we mean literally everything. The framework will type check keys used to inject args to make sure they map back to dependencies of the correct type. We do this without requiring you to use a single generic type (although we make great use of them under the hood on your behalf).
  3. Dependency replacement. Often times a dependency will need to be replaced. However, this can lead to issues when the new dependency is a different type than the old one. That's why we allow you to replace existing dependencies, but we do enforce types on replacements.
  4. Dumb consumers. We believe you shouldn't need to know if a dependency is a singleton, factory, etc. in order to use it.
  5. Free consumers. We believe you should be able to tell the framework how you want things resolved. There are times when you want to explicitly force the framework to give you a non-cached value (i.e. not a singleton). We allow you to make these decisions upon dependency resolution while still maintaining our other values.

Dependency types supported

  • values
  • factories
  • classes
  • promise values
  • async factories
  • async classes (normal classes that depend on async things)

Other features

  • singletons
  • dependency replacement
  • merging containers
  • forking containers