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

mangiafuoco

v1.2.3

Published

An efficient nodejs hooking system.

Downloads

11

Readme

MangiaFuoco

npm Build Status Coverage Status

This is a way to decouple application parts. It could be used to solve different use cases:

  1. Easily Collect metrics of your application
  2. Manipulate producer data multiple unknown modifiers
  3. Create Plug n Play components without altering already working codebase

Lets say you've a login function that returns a Promise containing the user information if the login suceeds.


function login(user, pass) {
  return userModel.findUser(user,pass);  
}

Later you realize you need to add an extra field to the returned data so you modify your code accordingly:

function login(user, pass) {
  return userModel.findUser(user,pass)
    .then(userObj => {
      userObj.loginTime = Date.now();
      return userObj;
    });
}

Then you want to coherce the user to change the password if that wasn't modified for some months.

function login(user, pass) {
  return userModel.findUser(user,pass)
    .then(userObj => {
      userObj.loginTime = Date.now();
      return userObj;
    })
    .then(userObjWTime => {
      if (userObjWTime.last_password_change + _30days < Date.now()) {
        userObj.mustChangePassword = true;
      } else {
        userObj.mustChangePassword = false;
      }
      return userObj;
    });
}

After 2 months. the boss gets to you and he says that he does not want to change it's password every month and you need to change your login function again adding even more complexity.

mangiafuoco to the rescue. What about having the login function doing something like:

function login(user, pass) {
  return userModel.findUser(user,pass)
    .then(userObj => projname.map('after_user_loggedin', userObj))
}

Adding additional stuff shouldn't change your login function code (and tests). And adding your boss last requirement should be as easy as adding your code in a separate file that should be testable by its own.

boss_exception.js


export function bossExceptionHandler(userObj, cback) {
 if (userObj.uid == 'boss') {
   userObj.mustChangePassword = false;
 }
 cback(null, userObj);
};

then registering your exception using something like this.

import {bossExceptionHandler} from './boss_exception';
projname.register(
  'after_user_loggedin',
  Handler.fromCback('boss_exception', bossExceptionHandler)
);