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

dject-core

v1.2.1

Published

Dject Core ==========

Downloads

75

Readme

Dject Core

Dject Core is the core dependency injection system for the Dject dependency injection container. This package is not intended to be used as a standalone DI container. Instead this is built to support the internal needs for the Dject system, allowing the rest of Dject to be built with good separation of concerns.

For more information on the Dject library, please see the following package:

https://www.npmjs.com/package/dject

API

New container creation

To create a new container, simply call the DjectCoreFactory function provided by the JS module:

// In node:
const container = require('dject-core')();

// In the browser:
const container = window.djectCoreFactory();

Registering a New Module

Module registration requires a name, a function which constructs the module and an array of dependency names (as strings). You can only register a module factory to a name once. Any subsequent registrations will throw an error. Module registration is chainable.

container
    .register('myDependency', () => { foo: 'bar' }, [])
    .register('anotherModule', (myDependency) => { baz: myDependency }, ['myDependency']);

container
    .register('myDependency', () => { foo: 'bar' }, [])
    .register('myDependency', () => { foo: 'bar' }, []); // Throws an error

Building Modules

Building a module can be done simply by calling the build method with the module name. This will construct all dependencies and the top-level module. Considering the registration example above, build will result in the following:

const myModuleInstance = container.build('anotherModule');

// produces the following:

// {
//     baz: {
//         foo: 'bar'
//     }
// }

Overriding Modules

Overriding a module is necessary for situations where a module has been registered, but you need to inject something different into the dependency tree. This is most common in testing scenarios.

container
    .register('myDependency', () => { foo: 'bar' }, [])
    .override('myDependency', () => { foo: 'bar' }, []); // Doesn't throw an error

Version History

1.0.0

Initial release