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

http-static-gzip-regexp

v0.0.2

Published

Middleware for using pre-compressed gzip files based on regexp url pattern

Downloads

13

Readme

http-static-gzip-regexp

Middleware for using pre-compressed gzip files based on regexp url pattern for Node.js

Serves compressed files for the given regexp url pattern. If the url requested matches the regular expression and the client accepts gzip encoding the the url is appended with ".gz" and the necessary headers are added.

Dynamic compression hurts performance of the server. Let the build tool handle compression, for example with grunt and the compress plugin: https://github.com/gruntjs/grunt-contrib-compress Use a similar regexp used during build time to load the compressed file just for files that are static. Not checking upfront if the .gz file exists removes the need to go to the os/disk for each request.

This solution can be used with any static server as long as this middleware is added first. This means it can be used with express static https://www.npmjs.org/package/express - but also with servers that supports caching like https://www.npmjs.org/package/express-static-cache and https://www.npmjs.org/package/st

You can still add dynamic compression for files that you don't have a static version for, just add the dynamic compression middleware layer after this one (ex. app.use(express.compress()))

Installation

  $ npm install connect-gzip-static
  

Usage

staticGzip =  require('http-static-gzip-regexp')

//Add the middleware express way:
app.use(staticGzip(/(\.html|\.js|\.css)$/));

//Add dynamic compression if you don't handle all files static
app.use(express.compress());

//Add a static web handler you prefer
app.use(express.static('path'));

Differences with similar modules:

  • https://www.npmjs.org/package/connect-gzip-static Checks if the .gz file exists on disk, requires extra call to the OS for each request. This is the server itself, can't be used with a server of choice.

  • http://pmuellr.blogspot.be/2013/11/gzip-encoding-and-compress-middleware.html Same idea but not yet in npm module. Also tested this repository with the wrk benchmarking tool. Benchmark according for you're own usecase: https://github.com/wg/wrk

License

MIT