43

Express and connect appeared to have removed their gzip functions because they were too inefficient. Are there any reliable solutions to gzip with express-js currently?

Improve this question
1
  • In case this is still relevant for someone: As I wanted to serve gziped static files but don't wanted the overhead of doing this on the fly i wrote a small wrapper on top of express.static, which allows serving allready gziped files. This would be useful if you integrated gzipping html/css/js files into your build process. Module can be found on npm: express-static-gzip Commented Nov 2, 2016 at 7:32

5 Answers 5

Reset to default
88

Express 3.0 now has compress() support:

var app = express(); // gzip app.use(express.compress()); // static app.use("/public", express.static(__dirname + '/public')); // listen app.listen(80);

EDIT for Express 4.0, compress become the separate middleware. So you have to install and import to use it:

var compress = require('compression'); app.use(compress());
Improve this answer
Sign up to request clarification or add additional context in comments.

5 Comments

Express 4.x removed almost all middleware, including compress. You can use Connect's compression middleware now: github.com/expressjs/compression.
does it require extra steps in heroku
In what circumstances does the compression trigger? I just added it but wrote res.send and no gzipped content came out. Does it require res.end or some other trigger?
Don't forget to add { threshold: 0 } when you want to compress static files with Express 4.x
Apart from run time template->html, is it good to use compression for .js and .css if we can compress them? Because it won't be good idea to use for SSR where bcoz of heavy traffic, it would have to compress for each file requested.. Can you please tell how to use compress just for .html? I'm using .ejs for templates.. @Spawnrider Also, I didn't add threshold: 0 for my .css or .js files, it worked right away
33

Connect 2.0 has added support for compress() middleware based on the new zlib stuff with that has just come out in Node Core API.

You can make use of this in your express server by adding a dependency to connect 2.0 in your package.json file:

{ ... dependencies: { "connect" : "2.x", "express" : "2.x", // etc.. } }

And then apply the following logic into your express app configuration:

// Create static file server with gzip support var app = express.createServer(express.logger()); app.use(connect.compress()); app.use(express.static(__dirname + '/public')); app.listen(80);

Please note that this stuff is still pretty new and while I could get it to work locally, my Heroku cloud application complained about the dependency on Compress 2.x during the pre-commit hook when deploying via git:

-----> Heroku receiving push -----> Node.js app detected -----> Resolving engine versions Using Node.js version: 0.4.7 Using npm version: 1.0.106 -----> Fetching Node.js binaries -----> Vendoring node into slug -----> Installing dependencies with npm npm ERR! Error: No compatible version found: connect@'>=2.0.0- <3.0.0-'

As you can see, they're still using an old version of node (0.4.7).

UPDATE:

Actually, I could get Heroku to deploy this by adding the corresponding engines section in the package.json:

{ ... "engines": { "node": ">= 0.6.0 < 0.7.0" } }

And these are the results when using a http compression tester:

enter image description here

UPDATE June 2014

Hiya, if you are reading this now. Dont forget that the stuff above is only relevant to Express 2.0.

Express 3.0 and 4.0 use different syntax for enabling http compression, see post by gasolin just below.

Improve this answer

4 Comments

@AndreyLushnikov: You have to use() compress before static. compress replaces res.write and res.end so that it can proxy data through zlib. If static is before compress, it handles the entire request before the compress middleware has a chance to run and patch the res methods. Steven, I've updated your answer to swap the use() calls.
@gasolin states below that Express 3.0 now has compress() support. If you're reading this, could you please update your answer?
How did you do the http compression tester?
The above provided link for the compression tester doesn't seem to be working anymore. Here is an alternative: gidnetwork.com/tools/gzip-test.php
5

I have also searched npm and found for example:

Gzippo has recently been developed(2 days ago) which I think is a good thing. I can't tell you about production usage. You should test/benchmark it yourself. I would also probably use a CDN for a live site or Nginx to host my static files instead of some nodejs module.

Improve this answer

1 Comment

We are using gzippo in production for a large UK newspaper. The beauty of configuring the content compression in the node layer is that you can then simply put Varnish, Squid or a CDN upstream and it will obey the http headers and keep a cached zipped copy on the proxy/CDN for all subsequent request. This keeps the cache config with your node code and in your git/svn etc.
3

Connect will support the new zlib stuff in Node in the next release

Improve this answer

Comments

1

If you've searched the npm you may have come across node-compress.

It shouldn't be too hard to inject it as middleware into express.

Improve this answer

2 Comments

There are plenty of compression libraries available, but I want to know if people are using them in production successfully.
@gAMBOOKa I'm using that one personally but not for production just for development.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.