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

hand-leftover

v0.2.2

Published

response 4xx 5xx, handover-plugin, compatible with connect

Downloads

10

Readme

hand-leftover

At the end of call chain, it send 404 or 500(when error exists). responsed html is customizable. written by coffeescript

Features

  • developer takes permission to control 404 / 500 response
  • prevent no answer from http server
  • compatible with connect

Why made this?

handover is fully compatible with connect's middleware. So, first my attempt is using errorhandler. but, in errorhandler , 404(page not found) is also Error ( it means I have to throw new Error '...')

My opinion about 404 is differnt. Page not found is naturally occured when all middleware didn't process request.

I need more flexible one.

Example


   server = http.createServer ho.make [
#      ... something you need
     leftover()
   ]

basic usages.


   server = http.createServer ho.make [
#      ... something you need
     leftover
       '404':
         html: "<h1> Page Not Found </h1>"
   ]

static html text is possible.


   server = http.createServer ho.make [
#      ... something you need
     leftover
       '404' :
         html: (callback)-> callback 'callback'
   ]

function is possible too.

    server = http.createServer ho.make [
      (req,res,next)-> next new Error 'Just Error' 
      leftover
        '500' :
          html: '500'
    ] 
# or 
    server = http.createServer ho.make [
      (req,res,next)-> next new Error 'Just Error' 
      leftover
        '500' :
          html: (error, callback)-> callback error.toString()
    ]

with error handler, it is also possible using text or function.

License

(The MIT License)

Copyright (c) 2014 junsik <[email protected]@google.com>

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the 'Software'), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED 'AS IS', WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.