Looking at the Future of Express: Using and Contributing to Express in 2020
summary
Explains that Express isn’t one module but a family (proxy-addr, path-to-regexp, compression, range-parser, serve-static) used across projects; shows a tiny polyfill that still gets 17.2 million downloads a week and maps work across expressjs/pillarjs/jshttp repos. Announces concrete plans to cut Express 5 and stage Express 6 within a year, add Promise-aware handler support, and launch a status board plus a paid triage/onboarding program with a hands-on workshop to recruit contributors and reduce maintainer burden.
AI-written summary · about
chapters (21)
- 0:00Introduction
- 0:40Fastif
- 4:50Doug Wilson
- 5:42Github Graph
- 7:31Wheres My Potato
- 8:06First Commit
- 8:41First Code Contribution
- 9:32Impact of Code
- 11:33Express in 2018
- 13:00Not a Potato
- 13:15Raising a Child
- 14:29The Future of Express
- 16:12The Project
- 17:51Package Maintenance Working Group
- 18:20The Express Project
- 19:31KOA
- 20:51Projects
- 22:44Open Issues
- 23:30Triage
- 26:32Funding
- 27:10Thank you
related talks
26mReviving Express: A challenging road for Express 5.0
38mExpress 101
22mDo You Even Need That Express Custom Server Any More?
44mNode & Express as Workflow Tools
49mNode.js Frameworks, or There and Back Again
21mPromises API in Node.js core: where we are and where we’ll get to
25mOpen Source Sustainability and our Corporate Social Responsibility
19mThe Road to Node.js