Upgrading make-dir from 4.x to 5.x
Comparison of the public API of make-dir 4.0.0 and 5.1.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 | 2 |
Removed exports
None detected.
Changed signatures
| export | Before | After |
|---|---|---|
make-dir · Options | interface | { readonly mode?: number | undefined; readonly fs?: any; } |
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 | >=10 | >=18 |
New exports (2)
| import | export | kind |
|---|---|---|
make-dir | makeDirectory | function |
make-dir | makeDirectorySync | function |
Frequently asked questions
What are the breaking changes when upgrading make-dir from 4 to 5?
Between make-dir 4.0.0 and 5.1.0, Vigia found 0 removed exports, 1 changed signatures and 0 removed or changed class or interface members.
What became deprecated in make-dir 5?
0 exports or members are newly marked as deprecated in make-dir 5.1.0.
For agents
GET https://vigia.coredls.cloud/v1/packages/npm/make-dir/upgrade?from=4.0.0&to=5.1.0