+6
Daily
+107
Weekly
69,680
stars
25,517
forks
1,752
watchers
2,746
prs
4,086
issues
167
releases
Top issues
#2818include "typings" field in package.json34 comments · 2015-11-30#2151Params registered on app available in routers used by app34 comments · 2014-05-29#2281'/' route breaks strict routing33 comments · 2014-08-05#1980Please add app.route('foo').use()31 comments · 2014-03-16#2501Add originalRoute like originalUrl30 comments · 2015-01-16#6711Restore Support for app.all('*') Wildcard in Express v523 comments · 2025-08-17#2896Define error-handling middleware functions explicitly (without arity detection)23 comments · 2016-02-19#3367Suggestion: Implicitly-named error handler22 comments · 2017-07-17
Discussions
#7591`[email protected]` rebuilds byte-for-byte from its provenance commit1 comments · 2026-11-10#7579Two different 429s from one Express middleware, and how a client should tell them apart0 comments · 2026-11-01#7570Two Express monitoring gotchas: load order and where the error handler goes0 comments · 2026-10-28#7524If `process.env.NODE_ENV` is not explicitly set, it returns `undefined` instead of `development`2 comments · 2026-10-16#7505Express 5.2.1 loading results on Node.js, Bun and Deno1 comments · 2026-10-05#7492React Frontend with Express: Server-Side Rendering or API-Based Architecture?1 comments · 2026-09-28#7413One-line idempotency middleware for Express1 comments · 2026-08-09#7359Express 5 + async/await: How to handle unhandled promise rejections without crashing?5 comments · 2026-07-04
Latest release
v5.3.0 v5.3.0 2026-10-09Highlights
🐞 Bug fixes
- Fixed HTTP header conflict between Content-Length and Transfer-Encoding in res.send - by @YuryShkoda in 4893
Fixed the behavior of res.send() to prevent conflicts between Content-Length and Transfer-Encoding HTTP headers in responses. The Content-Length header in res.send() is now only added when a Transfer-Encoding header is not present, complying with the HTTP specification that states both headers should not coexist in the same response. ETag generation is unaffected by the presence of a Transfer-Encoding header - by @cuishuang in 7459
Upgrade qs