Upgrading express from 4.x to 5.x
Comparison of the public API of express 4.22.3 and 5.2.1, computed automatically from their TypeScript types. A changed signature is a candidate for a breaking change, not a certainty.
Summary
| Removed import paths | 0 |
|---|---|
| Removed exports | 1 |
| Changed signatures | 0 |
| Removed class or interface members | 0 |
| Changed class or interface members | 0 |
| Newly deprecated | 0 |
| Requirement changes (engines, peer dependencies) | 1 |
| New exports | 0 |
Removed exports
| import | export | kind | Before |
|---|---|---|---|
express | query | function | (options: any): Handler |
Changed signatures
None detected.
Removed class or interface members
None detected.
Changed class or interface members
None detected.
Newly deprecated
None detected.
Requirement changes (engines, peer dependencies)
| Before | After | |
|---|---|---|
engines.node | >= 0.10.0 | >= 18 |
Frequently asked questions
What are the breaking changes when upgrading express from 4 to 5?
Between express 4.22.3 and 5.2.1, Vigia found 1 removed exports, 0 changed signatures and 0 removed or changed class or interface members.
What became deprecated in express 5?
0 exports or members are newly marked as deprecated in express 5.2.1.
For agents
GET https://vigia.coredls.cloud/v1/packages/npm/express/upgrade?from=4.22.3&to=5.2.1