Is connect-multiparty still maintained?

No — connect-multiparty stopped being maintained around September 2018. The ecosystem moved to multer, a separate project that took over the same job.

• replacement project
• medium confidence
• package successor

What should I use instead of connect-multiparty?

The ecosystem moved to multer, a separate project that took over the same job. multer is not a drop-in replacement, so expect to change call sites.

How to migrate from connect-multiparty to multer

Replace the middleware with multer({dest}); uploaded files move from req.files keyed by field name to multer's req.file / req.files shape, so file-handling code needs adjusting.

Why connect-multiparty is on this list

connect-multiparty wrapped the multiparty parser as Connect middleware; its last release was 2.2.0 in September 2018 and the Express team archived the repository on 14 May 2025 with an npm notice saying the package is archived and no longer maintained. The README already advised against it, saying "I actually recommend against using this module. It's cleaner to use the multiparty API directly", and warning that its temporary files are never cleaned up automatically. Most Express projects have settled on multer for multipart uploads.

The succession is well supported, but it is not the only defensible choice.

connect-multiparty alternatives

Beyond the primary recommendation, these are credible for connect-multiparty's use case:

• busboy — view on npm
• multiparty — view on npm
• formidable — view on npm

Check your own project for connect-multiparty

npx dead-deps --all --min-state unmaintained

Run that in the directory holding your lockfile. If connect-multiparty is anywhere in your tree — a direct dependency or buried under something else — it appears in the report with this verdict, this successor and the same evidence links, alongside anything else that has stopped moving. Nothing is uploaded; the scan reads your lockfile locally and queries public registry metadata.

Exit code 1 means something was flagged, which makes npx dead-deps --min-state deprecated usable as a CI gate. See how verdicts are produced.

Evidence

Every claim on this page traces to a primary source. Check them:

• Archived repository with the README recommendationgithub.com
• npm deprecation notice for connect-multipartynpmjs.com

Packages related to connect-multiparty

• casperjsReplacement project: playwright · unmaintained since March 2018
• phantomjs-prebuiltReplacement project: puppeteer · unmaintained since March 2018
• csurfReplacement project: csrf-csrf · unmaintained since January 2020
• enzymeReplacement project: @testing-library/react · unmaintained since December 2019
• event-streamNo direct successor · unmaintained since November 2018

See the full index of covered packages, or read the methodology for how a verdict is reached and why a quiet package is not a dead one.