Upgrading kind-of from 5.x to 6.x
Comparison of the public API of kind-of 5.1.0 and 6.0.3, 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 | 0 |
| Newly deprecated | 0 |
| Requirement changes (engines, peer dependencies) | 0 |
| New exports | 0 |
Removed exports
None detected.
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)
None detected.
Changelog between these versions
Text published by the package authors, shown as-is.
6.0.3
- Merge pull request #31 for issue #306.0.0
- refactor code to be more performant
- refactor benchmarksFrequently asked questions
What are the breaking changes when upgrading kind-of from 5 to 6?
Between kind-of 5.1.0 and 6.0.3, Vigia found 0 removed exports, 0 changed signatures and 0 removed or changed class or interface members.
What became deprecated in kind-of 6?
0 exports or members are newly marked as deprecated in kind-of 6.0.3.
For agents
GET https://vigia.coredls.cloud/v1/packages/npm/kind-of/upgrade?from=5.1.0&to=6.0.3