1.1.0 • Public • Published


"JavaScript dependency injection that's so small, it almost doesn't count."

Branch Status
Master Build Status Coverage Status NSP Status
All Build Status

What is Pluto?

Pluto is a JavaScript dependency injection tool.

Dependency injection is a spiffy way to assemble your applications. It decouples the various bits and makes your app testable. An introduction to dependency injection principles is currently beyond the scope of this guide.

Installing Pluto

Pluto is designed to be used with Node and NPM. From the root of a Node project, execute:

$ npm install pluto --save

How to Pluto?

A binder is the basic unit of Pluto's dependency injection. It maps names to objects you want.

Pluto's injection is done in a few steps:

  1. Create bindings. When you do this, you bind names to any combination of objects, factory functions and constructor functions.
  2. Optionally, call .get(...). Pluto will give you the thing mapped to that name. Along the way, it will inject parameters that match other names bound in the binder and resolve Promises as appropriate.
  3. Alternately, call .bootstrap() to run all your factory functions and constructors, and resolve all promises. This is handy if you're trying to start up an application with a bunch of moving parts, and more common than using .get(...) for each part individually.

There are three things you can bind to a name: an object instance, a constructor function and a factory function.


If you pass Pluto a promise, it will resolve it. If your factory or constructor function returns a promise, Pluto will resolve it before injecting the result into other components.

Instance Binding

The simplest binding is to bind a name to an instance:

const anInstance = {} // can be any JavaScript object, or a Promise
const bind = pluto()
// bind.get(...) gives us a Promise that resolves to our instance
bind.get('myInstance').then((myInstance) => {, anInstance)

Constructor Binding

You can also bind to a constructor function (i.e., a function that is meant to be used with the new keyword to create a new object). When you call .get(...), Pluto will invoke the Constructor using new and return the result. If the constructor has any parameters, Pluto will consult its bindings and pass them into the constructor:

function Greeter(greeting, name) {
  this.greeting = greeting = name
Greeter.prototype.greet = function () {
  return `${this.greeting}${}!`
const bind = pluto()
bind('name').toInstance(Promise.resolve('World')) // A promise will work, too
bind.get('greeter').then((myGreeter) => {, 'Hello, World!')

Factory Function Binding

Similarly, you can bind to a factory function -- that is, a function that creates some other object. When you call .get(...), Pluto will invoke the function and return the result. Just like with a constructor, if the factory function has any parameters, Pluto will consult its bindings and pass them into the factory:

function greeterFactory(greeting, name) {
  return function greet() {
    return `${greeting}${name}!`
const bind = pluto()
bind('name').toInstance(Promise.resolve('World')) // A promise will work, too
bind.get('greet').then((greet) => {, 'Hello, World!')

Author's note: Factory functions a super useful. I find that I use them more than any other type of binding.

Eager Bootstrapping

By default, Pluto will only create your objects lazily. That is, factory and constructor functions will only get called when you ask for them with .get(...).

You may instead want them to be eagerly invoked to bootstrap your project. For instance, you may have factory functions which set up Express routes or which perform other application setup.

Invoke .bootstrap() after creating your bindings to eagerly bootstrap your application. The result is a promise which resolves to a Map holding all bindings by name, fully resolved and injected.

function greeterFactory(greeting, name) {
  return function greet() {
    return `${greeting}${name}!`
const bind = pluto()
bind('name').toInstance(Promise.resolve('World')) // A promise will work, too
bind.bootstrap().then(app => {
  const greet = app.get('greet') // Note: it's synchronous. Everything is ready., 'Hello, World!')

Injected Objects are Singletons

Note that a factory function or constructor function is only called once. Each call to get(...) will return the same instance.

Remember that singletons are only singletons within a single binder, though. Different binders -- for instance, created for separate test methods -- will each have their own singleton instance.

Self injection

There are times when you might not know exactly what you'll need until later in runtime, and when you might want to manage injection dynamically. Pluto can inject itself to give you extra control.

There are two ways to inject Pluto. Use plutoBinder if you want the raw binder. Use plutoApp when you want the fully bootstapped, synchronous app.


The most direct -- and safe! -- way to self-inject Pluto is to ask for plutoBinder. This will inject the same bind function that you received when invoking pluto().

function fakeFactory(plutoBinder) {
  return plutoBinder.get('data') // will return a promise
const bind = pluto() // `bind` is the same object as `plutoBinder`, above
const actual = yield bind.get('factory'), 'test-data')

Note that the get(...) and getAll(...) functions are asynchronous and return a Promise!


When using Pluto's bootstrapping capability, you can self-inject the fully bootstrapped application under the name plutoApp:

class Greeter {
  constructor(plutoApp) {
    // Note: the plutoApp Map may not be fully populated yet, since we could
    // be at any indeterminate part of the bootstrapping process.
    // Save it for later, but don't go using it yet.
    this._plutoApp = plutoApp
  greet() {
    // By now, the app is fully bootstrapped and the plutoApp Map is safe
    // to use.
    const greeting = this._plutoApp.get('greeting')
    return `${greeting}, World!`
const bind = pluto()
const app = yield bind.bootstrap()
const greeter = app.get('greeter')
const actual = greeter.greet(), 'Bonjour, World!')


Under normal usage, this is pretty safe. There are a few corner cases to watch out for, however!

  1. You must call .bootstrap()! If not, or if you try to get an instance before bootstrapping, the plutoApp variable will not be defined.
  2. Save it for later. The sequence in which components are instantiated during the bootstrapping process is indeterminate. While the plutoApp variable is guaranteed to exist, it may not be fully populated until bootstrapping is completed. It will be safe to use during "normal" operation, however. Note: It would be easy to add a Promise that resolves when bootstrapping is complete. If you need this feature, ask for it!


npm i pluto

DownloadsWeekly Downloads






Last publish


  • botvinick