Upgrading lines-and-columns from 1.x to 2.x
Comparison of the public API of lines-and-columns 1.2.4 and 2.0.4, 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 | 1 |
| Removed class or interface members | 1 |
| Changed class or interface members | 0 |
| Newly deprecated | 0 |
| Requirement changes (engines, peer dependencies) | 1 |
| New exports | 0 |
Removed exports
| import | export | kind | Before |
|---|---|---|---|
lines-and-columns | default | class | class |
Changed signatures
| export | Before | After |
|---|---|---|
lines-and-columns · SourceLocation | { line: number; column: number; } | interface |
Removed class or interface members
| member | import | Before |
|---|---|---|
LinesAndColumns.string | lines-and-columns | any |
Changed class or interface members
None detected.
Newly deprecated
None detected.
Requirement changes (engines, peer dependencies)
| Before | After | |
|---|---|---|
engines.node | — | ^12.20.0 || ^14.13.1 || >=16.0.0 |
Frequently asked questions
What are the breaking changes when upgrading lines-and-columns from 1 to 2?
Between lines-and-columns 1.2.4 and 2.0.4, Vigia found 1 removed exports, 1 changed signatures and 1 removed or changed class or interface members.
What became deprecated in lines-and-columns 2?
0 exports or members are newly marked as deprecated in lines-and-columns 2.0.4.
For agents
GET https://vigia.coredls.cloud/v1/packages/npm/lines-and-columns/upgrade?from=1.2.4&to=2.0.4