Roadmap
The full plan is ROADMAP.md. It records a decision for every open upstream issue and pull request, and the research behind it is in research/.
Two lines
master, the compatible line: a drop-in replacement for Express 5.3.0 on Node.js 22, 24 and 26 (see the compatibility promise). Upstreammastergets merged in regularly.6.x, the next major: holds the breaking changes, andmastergets merged into it.
Order of work
- Foundation: vendoring
routerandsend, the differential harness and the benchmark harness. Done. - Tests: the safety net comes before the riskiest changes: coverage, the ecosystem and security suites, more differential scenarios, and mutation testing.
- TypeScript and dependencies: the code moves to strict TypeScript that Node.js runs directly, and users no longer need
@types/express. Small dependencies are replaced by what Node.js has built in, or forked. - Bug fixes, then performance, then additions, on the compatible line. Every bug fix has a regression test, and every speed-up has before and after numbers.
- Our 6.0, then HTTP/2.
Docs ride along with each item.
Rules every change follows
- Tests for the change, and a regression test that fails before and passes after for any bug.
- No difference from Express 5.3.0 in the differential harness, except the ones listed on purpose.
- Coverage stays at 100%, and the ecosystem suite passes.
- A benchmark run for any change to the code apps run.
- Upstream pull requests taken into the fork keep their authors.