Connect 3.0

Expected to be released after node v0.12 is released so we can drop node v0.8 support (support 2 latest versions). Deprecation warnings have been added to give developers time to migrate, specifically when using connect through express to avoid a major version bump. Please feel free to add any alternatives to removed middleware.

Note that if you're currently using connect.bodyParser(), you will still get the deprecation warning for multipart. For now, you can ignore it since you will only see the warning message once at start up. If you want to avoid any warning messages, do this instead:

app.use(connect.urlencoded())
app.use(connect.json())

Backwards Compatibility Changes

• Remove multipart middleware. By default, multipart downloads files to disk, which is deemed a security issue. Using multipart middleware as a stream (defer) became overly complex, and collaborators would rather have developers use a multipart parser directly. Since removing the defer option and only allowing developers to download multipart files to disk would cause concern, we opted to remove the entire multipart middleware instead. Use one of the following parsers or middleware instead:
  • formidable
  • connect-multiparty or multiparty
  • connect-busboy or busboy
• Remove staticCache. Use one of the following alternatives:
  • st
  • express-static-cache
• Remove limit middleware. No longer used by any of the parsers. It didn't work properly for streams2, so it's better built into the parser.
• Remove node 0.8 support. Connect 3 will be released after node v0.12 and will only support the latest 2 stable versions of node.
  • Remove pause utility
  • Remove any unnecessary patches in https://github.com/senchalabs/connect/blob/master/lib/patch.js