Upgrading send from 0.x to 1.x
Comparison of the public API of send 0.19.2 and 1.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 | 6 |
| Changed class or interface members | 0 |
| Newly deprecated | 0 |
| Requirement changes (engines, peer dependencies) | 1 |
| New exports | 0 |
Removed exports
| import | export | kind | Before |
|---|---|---|---|
send | mime | variable | any |
Changed signatures
None detected.
Removed class or interface members
| member | import | Before |
|---|---|---|
SendStream.etag | send | (val: boolean): SendStream |
SendStream.from | send | (paths: string): SendStream |
SendStream.root | send | (paths: string): SendStream |
SendStream.index | send | (paths: string | string[]): SendStream |
SendStream.hidden | send | (val: boolean): SendStream |
SendStream.maxage | send | (maxAge: string | number): SendStream |
Changed class or interface members
None detected.
Newly deprecated
None detected.
Requirement changes (engines, peer dependencies)
| Before | After | |
|---|---|---|
engines.node | >= 0.8.0 | >= 18 |
Frequently asked questions
What are the breaking changes when upgrading send from 0 to 1?
Between send 0.19.2 and 1.2.1, Vigia found 1 removed exports, 0 changed signatures and 6 removed or changed class or interface members.
What became deprecated in send 1?
0 exports or members are newly marked as deprecated in send 1.2.1.
For agents
GET https://vigia.coredls.cloud/v1/packages/npm/send/upgrade?from=0.19.2&to=1.2.1