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

wire-app

v1.0.7

Published

A tiny, but powerful dependency injection container for your Node.js apps

Downloads

10

Readme

wire-app

A tiny, but powerful dependency injection container for your Node.js apps

Features

  • manual registering of factory fuctions and classes
  • scanning directories for factory functions and classes to instantiate
  • setting values and getting values
  • injecting dependencies (duh)

Quick Example

const wireApp = require('wire-app');

wireApp('myCoolApp')
  .scan('./some/relative/dir')
  .scan('/some/absolute/dir')
  .register(taskRunner)
  .set('config', { my: 'values'})
  .on('error', (err) => console.error(err.message))
  .on('ready', (app) => {
    console.log(`${app.name} started!`);
    console.log(app.get('config'));
    app.get('taskRunner').run();
  });

API

The API is fluent. All functions, except get() can be chained.

wire-app(name)

Constructs a new app and returns it.

Example

wireApp('myApp')
  .on('ready', (app) => console.log(app.name)); // prints `myApp`

All other functions mentioned below are part of the 'app' API.

app.register(fn)

The register(fn) function will

  1. Invoke the fn parameter and inject its dependencies
  2. register it in the application context, under the function name.

The fn function should be a factory function OR a class, and must have a name.

The order you invoke the register functions does not matter. Wire-app will figure out dependency order.

The register(fn) function returns the app to provide a fluent API.

See this example

app.scan(scanPath)

Scans recursively am absolute or relative directory for exposed factory methods and/or classes. It will register them, similar to the app.register(fn) function

The app.scan(scanPath) function returns the app to provide a fluent API.

See this example

app.set(key, value)

Stores a value, under a certain key, in the application context

The value can be of any type. No dependency injection will occur

The app.set(key, value) function returns the app to provide a fluent API.

app.get(key)

Returns the value (or component) registered under the requested key.

app events

The app is an EventEmitter and will emit a few events

'ready'

This event is emitted when the whole application was wired successfully.

It emits the app as its first parameter

'error'

Will be emitted when something went wrong during the wiring phase.

Thanks

The idea of the API comes from Dieter Luypaert.