Upgrading ansi-regex from 5.x to 6.x
Comparison of the public API of ansi-regex 5.0.1 and 6.4.0, 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 | 1 |
| 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
| export | Before | After |
|---|---|---|
ansi-regex · Options | interface | { readonly onlyFirst: boolean; } |
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 | >=8 | >=12 |
New exports (1)
| import | export | kind |
|---|---|---|
ansi-regex | default | function |
Frequently asked questions
What are the breaking changes when upgrading ansi-regex from 5 to 6?
Between ansi-regex 5.0.1 and 6.4.0, Vigia found 0 removed exports, 1 changed signatures and 0 removed or changed class or interface members.
What became deprecated in ansi-regex 6?
0 exports or members are newly marked as deprecated in ansi-regex 6.4.0.
For agents
GET https://vigia.coredls.cloud/v1/packages/npm/ansi-regex/upgrade?from=5.0.1&to=6.4.0