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

lactate

v0.13.12

Published

Simple and featureful assets server

Downloads

257

Readme

Lactate

Very simple static file handler, with a few electives.

npm install lactate

Example

Just pass three arguments to the serve function (path, request, response). Lactate will stream your file to the client in the most efficient way, by piping: readFile > gZip > response.


var express = require('express')
var app = express.createServer()
var lactate = require('lactate')()

app.get('/', function(req, res) {
  reurn lactate.serve('pages/land.html', req, res)
})

app.get('/files/*', function(req, res) {
  return lactate.serve(req.url.substring(1), req, res)
})

app.get('/images/:img', function(req, res) {
  var img = req.params.img
  return lactate.serve('thumbs/'+img, req, res)
})

app.listen(8080)

##Options

Options can be passed to the initialization function or using the set method.


//Passing to initialization function
var lactate = require('lactate')({expires:172800})

//Set method
lactate.set('expires', null)

//Either function accepts (key, value) or an object.

Available options are currently cache (boolean), expires (seconds), and debug.

The cache option will have Lactate save your files in memory. By default this is enabled, and there's no great reason to disable it.

Setting expires will have Lactase set appropriate Expires and Cache-Control headers for client-side caching. This option represents seconds-from-now to expire.

Debugging

Debugging is level-based. The debug function accepts a number and a callback function, or a boolean. By default, the debugging function is console.log. The following syntaxes are valid.


var lactate = require('lactate')({
  debug:true
})

lactate.set('debug', 0, function(level, msg, path, statusCode) {
  /* 
    Do stuff

    Note however that statusCode arguments are only
    given for level 0 listeners
  */
})

lactate.set('debug', 1, console.log)
lactate.set({debug:false})

More robust debugging will come in the future as I isolate the functionality into a module of its own.

##TODO

  • Express middleware
  • Expiration defaults, e.g. 'two days,' 'one month'
  • Redis integration
  • Standalone server