Huge News!Announcing our $40M Series B led by Abstract Ventures.Learn More
Socket
Sign inDemoInstall
Socket

ahoy-di

Package Overview
Dependencies
Maintainers
1
Versions
16
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

ahoy-di

A flexible dependency injection (DI) container for Node

  • 3.0.0
  • latest
  • npm
  • Socket score

Version published
Weekly downloads
4
decreased by-80.95%
Maintainers
1
Weekly downloads
 
Created
Source

Ahoy-DI

A flexible dependency injection (DI) container for Node


Given a collection of services, Ahoy-DI will automatically load and connect them together in the appropriate order based on their specified dependencies. When a service that returns a promise is encountered, the setup process will wait until the promise is resolved before continuing.

If you're familiar with the dependency injection system used by AngularJS, you'll feel right at home.

Services

First, let's look at a simple service that has no dependencies. In this example, our service is declared to be a singleton. As a result, all services that rely upon this service will share the same instance.

exports = module.exports = function() {

    return new class {
        start() {
            console.log('Car is starting.');
        }
    };

};

exports['@singleton'] = true;
exports['@require'] = [];

Next, let's pair two services together. In this example, we have created a foo service that relies upon the bar service.

services/foo.js

exports = module.exports = function(bar) {

    return () => {
        console.log('Foo.');
        bar();
    };

};

exports['@singleton'] = true;
exports['@require'] = ['bar'];

services/bar.js

exports = module.exports = function() {

    return () => {
        console.log('Bar.');
    };

};

exports['@singleton'] = true;
exports['@require'] = [];

Wiring Services Together

The simplest method by which Ahoy-DI can be configured is to point it at a directory containing your application's services. When a service exists within a directory, the name of that directory will determine the service's name. When a service exists as a standalone file, the base name of the file will determine the service's name.

In this example, three services are loaded - foo, bar, and beep.

/**
 * File structure:
 *
 * index.js (this script)
 * ./services
 *     foo/index.js
 *     bar/index.js
 *     beep.js
 */

const Ahoy = require('ahoy-di');
const path = require('path');

const container = new Ahoy({
    'services': path.resolve(__dirname, 'services')
});

container.load('foo')
    .then((foo) => {
        foo.herp();
    })
    .catch((err) => {
        console.log(err);
        process.exit(1);
    });

Loading Services from Multiple Directories

You may also pass an array of service directories the Ahoy-DI. In the event that a service with the same name is defined in multiple locations, the last one to be defined will take precedence. Service directories are parsed in the order in which they are passed.

const Ahoy = require('ahoy-di');
const path = require('path');

const container = new Ahoy({
    'services': [
    	path.resolve(__dirname, 'services'),
    	path.resolve(__dirname, 'more-services'),
    ]
});

container.load('foo')
    .then((foo) => {
        foo.herp();
    })
    .catch((err) => {
        console.log(err);
        process.exit(1);
    });

Loading Services by Name

Individual services can also be defined by name. In the event that a service with the specified name has already been located elsewhere, the service that has been defined by name will always take precedence.

const Ahoy = require('ahoy-di');
const path = require('path');

const container = new Ahoy({
    'services': [
    	path.resolve(__dirname, 'services'),
    	path.resolve(__dirname, 'more-services'),
    ]
});

container.service('car', require('./misc/car'));

container.load('foo')
    .then((foo) => {
        foo.herp();
    })
    .catch((err) => {
        console.log(err);
        process.exit(1);
    });

Constants

In addition to defining services, you can also define constants. The following example illustrates this concept.

const Ahoy = require('ahoy-di');
const path = require('path');

const container = new Ahoy({
    'services': path.resolve(__dirname, 'services')
});

/**
 * Each of your services can now access the `settings` object we have defined here
 * in the same way that they would access any other service.
 */
container.constant('settings', {
    'make': 'Jeep',
    'model': 'Grand Cherokee',
    'year': '2017'
});

container.load('foo')
    .then((foo) => {
        foo.herp();
    })
    .catch((err) => {
        console.log(err);
        process.exit(1);
    });

Dynamic Fetching

After your dependency injection container has been configured and initialized, dynamic fetching allows modules that are external to your container to obtain references to the services that exist within it.

To enable dynamic fetching, assign a unique ID to your container instance via the id property and set the extendRequire property to true. Once your container has initialized, you can then obtain references to your services via Node's built-in require() method, as shown in the following example. In this instance, assigning an ID of container allows us to reference our services via require('container/[service-name-here]').

# See examples/example5
const Ahoy = require('ahoy-di');
const path = require('path');

const container = new Ahoy({
    'id': 'container',
    'extendRequire': true,
    'services': [
        path.resolve(__dirname, 'services')
    ]
});

container.load('foo')
    .then((foo) => {
        foo();
		require('container/bar')();
    })
    .catch((err) => {
        console.log(err);
        process.exit(1);
    });

Forced Loading

By passing an array of service names to our container via the load property, we can specify that those services must be initialized, even if they are not referenced by any other services within our container.

Use cases:

  • A stand-alone service that performs important functionality, but for which no dependent services exist.
  • A service for which no dependent services (within our container) exist, but for which external modules will want to obtain a reference after our container has been initialized.
# See examples/example6
const Ahoy = require('ahoy-di');
const path = require('path');

const container = new Ahoy({
    'id': 'container',
    'extendRequire': true,
    'services': [
        path.resolve(__dirname, 'services')
    ],
    'load': ['herp']
});

container.load('foo')
    .then((foo) => {
        foo();
		require('container/herp');
    })
    .catch((err) => {
        console.log(err);
        process.exit(1);
    });

FAQs

Package last updated on 20 Dec 2018

Did you know?

Socket

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Install

Related posts

SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap
  • Changelog

Packages

npm

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc