Upgrading detect-libc from 1.x to 2.x
Comparison of the public API of detect-libc 1.0.3 and 2.1.2, 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 | 3 |
| Removed class or interface members | 0 |
| Changed class or interface members | 0 |
| Newly deprecated | 0 |
| Requirement changes (engines, peer dependencies) | 1 |
| New exports | 3 |
Removed exports
| import | export | kind | Before |
|---|---|---|---|
detect-libc | method | variable | "" | "getconf" | "ldd" | "filesystem" |
Changed signatures
| export | Before | After |
|---|---|---|
detect-libc · family | "" | "glibc" | "musl" | (): Promise<string | null> |
detect-libc · version | string | (): Promise<string | null> |
detect-libc · isNonGlibcLinux | boolean | (): Promise<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 | >=0.10 | >=8 |
New exports (3)
| import | export | kind |
|---|---|---|
detect-libc | familySync | function |
detect-libc | versionSync | function |
detect-libc | isNonGlibcLinuxSync | function |
Frequently asked questions
What are the breaking changes when upgrading detect-libc from 1 to 2?
Between detect-libc 1.0.3 and 2.1.2, Vigia found 1 removed exports, 3 changed signatures and 0 removed or changed class or interface members.
What became deprecated in detect-libc 2?
0 exports or members are newly marked as deprecated in detect-libc 2.1.2.
For agents
GET https://vigia.coredls.cloud/v1/packages/npm/detect-libc/upgrade?from=1.0.3&to=2.1.2