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

dosage

v1.0.0

Published

Obvious dependency injection for javascript

Downloads

4

Readme

dosage

Master branch build status Published version ISC Licensed

dosage provides a super simple (36 loc!) api for a javascript dependency injection container. This is my opinionated take on how to do DI containers in javascript, I don't have an opinion about whether or not you should use it.

import dosage from "dosage";
const di = dosage();

di.register("foo", () => new Foo());
di.register("bar", di => new Bar(di.get("foo")));
di.singleton("baz", () => new Baz());

/* fast forward to... */
const foo = di.has("foo") ? di.get("foo") : "Nope";

API

Putting things in the container

The API is designed to be as simple as possible, but no more so. The register method lets you store things against keys in the container. The key can be any javascript value. If you provide a callback for the second argument to register, it will be invoked every time that key is accessed with the return value of the callback being returned (allowing you to have lazily loaded "services"). The callback is invoked with the container object as a sole argument, allowing you to fetch further dependencies according to arbitrary logic inside your callback. If you provide anything other than a callback as a second argument it will be returned as-is each time the key is accessed (this gives you a basic singleton pattern). If you need lazy-loaded singletons, use the singleton method in place of register. This will guarantee the provided callback is called at most once (you can use the singleton method with non-callback values too, but then it's functionally identical to register).

const foo = {a, b, c};
/* simple value store with arbitrary keys */
di.register(foo, 100);
/* lazy loading */
di.register(foo, () => new Foo());
/* singleton with dependencies */
di.singleton("bar", di => new Bar(di.get(foo)));
/* pointless, just use register for values */
di.singleton("baz", new Baz());

Getting things out

You can use the has method to see if a key is registered in the container. Using has won't invoke any callbacks. Use get to access the value of that key.

di.register("foo", () => "bar");
di.has("foo"); // true
di.has("other"); // false
di.get("foo"); // "bar"

Install

npm install dosage
# optionally run tests (you'll need tap installed)
npm test