Upgrading parse-json from 7.x to 8.x
Comparison of the public API of parse-json 7.1.1 and 8.3.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 | 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 |
|---|---|---|---|
parse-json | ReviverFn | type | ((this: any, key: string, value: any) => any) | undefined |
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 | >=16 | >=18 |
New exports (1)
| import | export | kind |
|---|---|---|
parse-json | Reviver | type |
Frequently asked questions
What are the breaking changes when upgrading parse-json from 7 to 8?
Between parse-json 7.1.1 and 8.3.0, Vigia found 1 removed exports, 0 changed signatures and 0 removed or changed class or interface members.
What became deprecated in parse-json 8?
0 exports or members are newly marked as deprecated in parse-json 8.3.0.
For agents
GET https://vigia.coredls.cloud/v1/packages/npm/parse-json/upgrade?from=7.1.1&to=8.3.0