Upgrading raw-body from 3.x to 4.x
Comparison of the public API of raw-body 3.0.2 and 4.0.0, 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 | 0 |
| Changed signatures | 0 |
| Removed class or interface members | 0 |
| Changed class or interface members | 4 |
| Newly deprecated | 0 |
| Requirement changes (engines, peer dependencies) | 1 |
| New exports | 7 |
Removed exports
None detected.
Changed signatures
None detected.
Removed class or interface members
None detected.
Changed class or interface members
| member | Before | After |
|---|---|---|
Options.encoding | Encoding | null | undefined | false | Encoding | null | undefined |
RawBodyError.type | string | RawBodyErrorType | undefined |
RawBodyError.status | number | number | undefined |
RawBodyError.statusCode | number | number | undefined |
Newly deprecated
None detected.
Requirement changes (engines, peer dependencies)
| Before | After | |
|---|---|---|
engines.node | >= 0.10 | >=22 |
New exports (7)
| import | export | kind |
|---|---|---|
raw-body | Decoder | interface |
raw-body | default | function |
raw-body | getRawBody | function |
raw-body | getRawBodyWeb | function |
raw-body | RawBodyErrorType | type |
raw-body | WebRawBodyStream | type |
raw-body | NodeRawBodyStream | type |
Frequently asked questions
What are the breaking changes when upgrading raw-body from 3 to 4?
Between raw-body 3.0.2 and 4.0.0, Vigia found 0 removed exports, 0 changed signatures and 4 removed or changed class or interface members.
What became deprecated in raw-body 4?
0 exports or members are newly marked as deprecated in raw-body 4.0.0.
For agents
GET https://vigia.coredls.cloud/v1/packages/npm/raw-body/upgrade?from=3.0.2&to=4.0.0