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 🙏

© 2026 – Pkg Stats / Ryan Hefner

care-fully

v1.0.2

Published

This library allows you to have re usable logic in your express application that is able to stack on top of each other.

Readme

Care-Fully

A Chainable way to respond to express request.

This library allows you to have re usable logic in your express application that is able to stack on top of each other.

It manages all of your async code so that you can just ask for what you need and perform validation.


import express from "express"
const app = express();
import jwt from "jsonwebtoken"
import SECRET from "./secret";
import {Respond} from "care-fully"

import ProfileRepo from "./repo/Profile"


//interface

import {User} from "./user-interface"
import {Profile} from "./user-profile-interface";


const userR = Respond.Append({
    user({req}){
        const user = jwt.verify(req.headers.token,SECRET)
        return user as User
    }
}).catch(({error,res})=>{
    //handle error here, nothing else will respond
    res.status(403).send({
        message:"fobidden"
    })
})

const profileR = userR.append({
    /**
     * This comes from the previous response and is reuse. 
     * You will get any type information was passed down.
     */
    async profile({user}){
        //type checking available 
        const profile = await ProfileRepo.getUserProfile(user)
        if(!profile){
            throw new Error("user profile has not been created")
        }else{
            return profile
        }
    }
}).correct({
    async profile({user}){
        //create new profile for user
        const profile = await ProfileRepo.createUserProfile(user);
        return profile as Profile
    }
}).catch(({res})=>{


    res.status(500).json({
        message:"failed to create user profile"
    })
})


app.post("/user/profile",Respond.MergeAll(profileR).data(({profile})=>{
    //this is the user profile
    return profile;
})


/**
 * User response is a 200 response with the user profile
 * 
 * /

This allows you to abstract out all of the things your server has to do so you can reuse them later on.

Getting the user can be user later on as well, in different api response.

Static Methods

MergeAll

one or more handlers can be joined togather to receive all the appended data. Merged handlers are run in parallel

ConcatAll

one or more handlers can be joined togather to receive all the appended data. Concat handlers are run in one after each other. Even if they are async

Good

Automatically respond with a 200 ok message if nothing throws an error

   Respond.Append(...info...).good(async({info})=>{
       await sendEmail(info)
   })

Data

Automatically respond with a 200 message containing what ever data was returned

   Respond.Append(...info...).data(({info})=>{
       return format(info);
   })