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

binder

v2.0.5

Published

Simple, yet powerful IoC container and service locator for both, the browser and node.

Downloads

169

Readme

Binder

Simple, yet powerful IoC container and service locator for both, the browser and node. Inspired by Illuminate/Container.

Installation

NPM users:

> npm i binder

YARN users:

> yarn add binder

Usage

While we miss a documentation website for this, you can simply check out the following example.

You can also refer to the test cases and the Container API, which is pretty easy

import { Container } from 'binder'
const container = new Container()

class User {
  constructor({ email, password }) {
    this.email = email.toLowerCase().trim()
    this.password = password.trim()
  }
}

/**
 * This class is bound to the container using a factory function
 * that passes a Connection object as its dependency 
 */
class UserRepository {
  constructor(connection) {
    this.db = connection;
  }

  async create({ email, password }) {
    const user = new User({ email, password })
    await UserRepository.validate(user)

    return this.db.insert(user.toJSON())
  }

  async findById(id) {
    const user = await this.db.select('email', 'password').where({ id })

    if (user) return new User(user)

    return null
  }

  static validate({ email, password }) {
    if (!email) throw new TypeError('Email is required')
    if (!password) throw new TypeError('Password is required')
  }
}

/**
 * This class is directly bound to the container, which injects itself
 * as the first param whenever the class is resolved. 
 */
class UserController {
  constructor(container) {
    // UserRepository is resolved by reference, so we have intellisense support!
    this.userRepo = containger.get(UserRepository)
  }

  // Simple handler for an express route, using the controller's instance
  async createUser(req, res) {
    const { email, password } = req.body;
    try {
      const user = await this.userRepo.create({ email, password })
      res.send({ user })
    } catch (err) {
      const { stack, ...error } = err
      res.status(400).send({ error })
    }
  }

  async getUser(req, res) {
    const { id } = req.body;
    try {
      const user = await this.userRepo.findById(id)
      if (user === null) {
        throw Object.assign(new Error(`User ${id} not found`), { status: 404 })
      }

      res.send({ user })
    } catch (err) {
      const { stack, status = 500, ...error } = err
      res.status(status).send({ error })
    }
  }
}

/**
 * We want to share the same instance of UserRepository, 
 * hence we bind it as a singleton, otherwise we'd use .bind()
 * 
 * We can provide a factory function as the second param
 * to resolve its dependencies (also from the container).
 */
container.singleton(UserRepository, (container) => {
  const connection = container.get('db').table('users')
  return new UserRepository(connection)
})

/**
 * Because UserController depends directly on the Container,
 * we can simply pass its class to either .get() or .make() methods.
 * The Container will know how to resolve and return an instance of it
 */
container.singleton(UserController)

// Example usage with an Express application (you may want to use a middleware instead)
app.post('/users', (req, res) => container.get(UserController).createUser(req, res))
app.post('/users/:id', (req, res) => container.get(UserController).getUser(req, res))