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

boost_library

v1.0.4

Published

A simple Spring 'like' Dependency injection container & optionally express wrapped server.

Downloads

9

Readme

Boost Libary

A simple Spring 'like' Dependency injection container & optionally express wrapped server.

Boost functions:

$Component

You can use this function to register a key/value Object that can be retrieved:

 $Component({
     key: 'IService',
     name: 'service.impl.v1',
     dependencies: ['IAnotherService'],
     injector: ({IAnotherService }) =>{
         //some code
     },
 })

$Controller

Controllers are functionally the same as components the only difference controllers will be searched and instantiated at run time to run the express server. All exported functions out of controller will be registered as express routes.

  $Controller({
     key: 'IController',
     name: 'controller.impl.v1',
     dependencies: ['IAnotherService'],
     injector: ({IAnotherService }) =>{
         const service = {};

         service.ping = {
             method: 'GET',
             path: '/ping',
             call: (req, res) => {
                 //Some code
             }
         }
         return service; 
     },
 })

$ComponentScan;

Component Scan allows the container to scan your paths to find dependencies. You must supply basepackage paths in order for them to be picked up.

$ComponentScan({
    basePackages: [__dirname + '/somepath',
    then: () => {
        //do some code 
        //Typically you can begin running your app at this point
    }
})

get

get will attempt to retrieve a dependency by key

get({key: 'ISevice'})

getListOfComponentNames

Function will retrieve a list of names for all registered dependencies in the container.

validate

Function will inspect each dependency for dependencies and throw errors if not well formed.

registerPreEndpointHandlers

Function for passing in pre handle middleware

registerPostEndpointHandlers

Function for passing in post handle middleware

run

Function for running the app and starting the express server;