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