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 🙏

© 2025 – Pkg Stats / Ryan Hefner

static_file_handler

v0.0.41

Published

static_file_hander ====

Downloads

10

Readme

static_file_hander

Point an http server to this to handle serving files from a folder, with ETag support.

Perhaps the best thing about this solution is it handles on the fly checking of file time and size (using fs.lstat) and requires no additional npms.

Instalation

npm install --save static_file_hander

Examples

A brief single statement example would be:


    var server =  require('http').createServer(require('static_file_handler').getStaticFileHandler({
            paths:{
                default:"./html/readme.html"}
        })
    ).listen(8080);

Paths can contain different folders based on extension (typically used to specify a different location for scripts)

You must specify a default, which can either be a filename (meaning that's the home page, and it's in the root web folder), or a folder name (it will look for one of index.html,index.htm,home.html,home.htm, in that folder).

If you specify a favicon, it and the file does not exist, it will be replaced with a default icon that's in the html folder of the demo that ships with the source.

A complex example might be

     var statics = require('static_file_handler');
     var server = require('http').createServer(statics.getStaticFileHandler({
 
         ramcache: {
             "/hello.world": {
                 headers: {
                     "200": {
                         ETag: "nerds.rule"
                     }
 
                 },
                 content: "hello world",
                 mimeType: "text/plain"
             },
             "/random": {
                 headers: {
                     "200": {}
                 },
                 content: function () {
                     return Math.random().toString()
                 },
                 mimeType: "text/plain"
             }
         },
         paths: {
             favicon: "./html/image/mysite.ico",
             js: {
                 files: "./js/",
                 cache: "./jscache/"
             },
             default: "./html/readme.html"
         },
         handlers: {
 
             "200": function (req, res, toSend, stat) {
 
                 // do something here with toSend.path, toSend.headers, examine stat
                 // optionally set toSend.content, which will force a one time send of something other than the file.
                 // (unless it happens to be an entry you have defined in ramcache, in which case the content will be persistent.
                 // until you change it again.
                 
                 // the "includedfile" npm uses this to unlify, and merge dependant files on the fly, keeping the result in a cache folder.
 
                 // if we updated the file and it's date and or size has changed, call this to
                 // rebuild the ETags (otherwise client may not get updated version as it's etag will match 
                 // what's currently in toSend.
                 statics.defaultRefreshCacheEntry(toSend, stats);
 
                 return statics.default200Handler(req, res, toSend, stats);
             }
 
         }
     })).listen(8080);