Comparison of the public API of yallist 4.0.0 and 5.0.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
4
Changed signatures
1
Removed class or interface members
0
Changed class or interface members
2
Newly deprecated
0
Requirement changes (engines, peer dependencies)
1
New exports
1
Removed exports
import
export
kind
Before
yallist
create
other
yallist
prototype
variable
any
yallist
ForEachIterable
interface
interface
yallist
NodeConstructor
interface
interface
Changed signatures
export
Before
After
yallist · Node
interface
class
Removed class or interface members
None detected.
Changed class or interface members
member
Before
After
Node.next
Node<T> | null
Node<T> | undefined
Node.prev
Node<T> | null
Node<T> | undefined
Newly deprecated
None detected.
Requirement changes (engines, peer dependencies)
Before
After
engines.node
—
>=18
New exports (1)
import
export
kind
yallist
Yallist
class
Frequently asked questions
What are the breaking changes when upgrading yallist from 4 to 5?
Between yallist 4.0.0 and 5.0.0, Vigia found 4 removed exports, 1 changed signatures and 2 removed or changed class or interface members.
What became deprecated in yallist 5?
0 exports or members are newly marked as deprecated in yallist 5.0.0.
For agents
GET https://vigia.coredls.cloud/v1/packages/npm/yallist/upgrade?from=4.0.0&to=5.0.0