Upgrading yocto-queue from 0.x to 1.x
Comparison of the public API of yocto-queue 0.1.0 and 1.2.2, 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 | 1 |
Removed exports
| import | export | kind | Before |
|---|---|---|---|
yocto-queue | prototype | variable | any |
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 | >=12.20 |
New exports (1)
| import | export | kind |
|---|---|---|
yocto-queue | default | class |
Frequently asked questions
What are the breaking changes when upgrading yocto-queue from 0 to 1?
Between yocto-queue 0.1.0 and 1.2.2, Vigia found 1 removed exports, 0 changed signatures and 0 removed or changed class or interface members.
What became deprecated in yocto-queue 1?
0 exports or members are newly marked as deprecated in yocto-queue 1.2.2.
For agents
GET https://vigia.coredls.cloud/v1/packages/npm/yocto-queue/upgrade?from=0.1.0&to=1.2.2