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

@dmitriyzverev/pod

v1.0.0-dev.0

Published

_Simple implementation of Service Locator pattern with singletons and lazy loading_

Downloads

2

Readme

@dmitriyzverev/pod

Simple implementation of Service Locator pattern with singletons and lazy loading


Intro

There are two main entities: pod and seed. Pod is a container for seeds. Seed is a function that get pod as an argument and returns some value. Seed can use any other seed from pod as a dependency. It is a way to organize your code into small pieces, that can be easily tested and reused.

Usage

  1. Install dependencies:

    npm i -SE @dmitriyzverev/pod
  2. Create pod and define your seeds inside:

    import {createPod} from '@dmitriyzverev/pod';
    const pod = createPod({
        seeds: {
            get user() {
                return {
                    name: 'Bob',
                };
            },
            get helloMessage() {
                return `Hello, ${pod.user.name}!`; // use "user" seed as a dependency
            },
        },
    });

    Now you can use any seed defined in pod:

    console.log(pod.helloMessage); // Hello, Bob!

Advanced usage

Singletons

By default, each seed is a singleton. It will be created only once, and only if requested. If you need to create a new seed instance for each seed request, disable the seed singleton in the singletons property:

import {createPod} from '@dmitriyzverev/pod';
const pod = createPod({
    seeds: {
        get user() {
            return {
                name: 'Bob',
            };
        },
    },
    singletons: {
        user: false, // disable singleton for "user" seed
    },
});
console.log(pod.user === pod.user); // false - each request creates a new instance

Exclude and include seeds

If you need to exclude some seeds from pod, use exclude property:

import {createPod} from '@dmitriyzverev/pod';
const pod = createPod({
    seeds: {
        get foo() {
            return 'foo';
        },
        get bar() {
            return 'bar';
        },
        get baz() {
            return 'baz';
        },
    },
});
const podWithoutFoo = pod.exclude('foo');
console.log(podWithoutFoo.foo); // undefined

Or you can include only some seeds:

const podWithFooAndBar = pod.include('foo', 'bar');
console.log(podWithFooAndBar.foo); // 'foo'
console.log(podWithFooAndBar.baz); // undefined

Both exclude and include methods create a new pod instance, so you can use them and don't worry about the original pod:

console.log(pod.foo); // 'foo' - still available in the original pod