Upgrading mime from 3.x to 4.x
Comparison of the public API of mime 3.0.0 and 4.1.0, computed automatically from their TypeScript types. A changed signature is a candidate for a breaking change, not a certainty.
Summary
| Removed import paths | 2 |
|---|---|
| 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 | 2 |
Removed import paths
| Removed import paths |
|---|
mime/Mime |
mime/lite |
Removed exports
| import | export | kind | Before |
|---|---|---|---|
mime | TypeMap | interface | interface |
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 | >=10.0.0 | >=16 |
New exports (2)
| import | export | kind |
|---|---|---|
mime | Mime | class |
mime | default | variable |
Frequently asked questions
What are the breaking changes when upgrading mime from 3 to 4?
Between mime 3.0.0 and 4.1.0, Vigia found 1 removed exports, 0 changed signatures and 0 removed or changed class or interface members.
What became deprecated in mime 4?
0 exports or members are newly marked as deprecated in mime 4.1.0.
For agents
GET https://vigia.coredls.cloud/v1/packages/npm/mime/upgrade?from=3.0.0&to=4.1.0