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

zero-respond

v0.0.13

Published

This module handles respond of request when you use bus in your request handler.

Downloads

60

Readme

zero-respond

This module handles responding of request when you are using bus in your request handler.

Usage

  1. Add dependency to your module package.json file like:
{
	"name" : "YOUR_MODULE_NAME",
	"zero" : {
		"dependencies" : {
			"respond" : "^0.0.1"
		}
	}
}
  1. Set bus data named respond in your request' bus. Respond module adds a router handler which will always be called at last of every request, and read from data of bus to decide what to respond. Codes for more detail :
module.exports = {
    route : {
        "GET /anyRoute" : function( req, res){
            //bus.fcall() fires two event automatically, one before and one after your main business logic
            //In this case, it fires `someEvent.before` and `someEvent.after`
            req.bus.fcall("someEvent", arg1, arg2, function(){
                //deal what you want to do

                //respond module handlers 3 type of output, `data`, `file` and `page`. Which to output depend on your bus data.

                //1.Output data as json.
                req.bus.data("respond.data",{"key":"value})

                //2.Render page with data, and output html as result.
                req.bus.data("respond.data", DATA_FOR_PAGE_RENDERING)
                req.bus.data("respond.page", TEMPLATE_LOCATION)

                //3. Send file to client
                req.bus.data("respond.fire", FILE_LOCATION)
            })
        }
    }
}

We strongly suggest you to use respond module to handle respond for you rather then using res in you request handler, because in this way other modules can modify or inject data to output easily. Plus, all data modification can be traced and nicely shown by dev tool.