Upgrading camelcase from 8.x to 9.x
Comparison of the public API of camelcase 8.0.0 and 9.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 | 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 | 0 |
Removed exports
None detected.
Changed signatures
| export | Before | After |
|---|---|---|
camelcase · Options | { readonly pascalCase?: boolean | undefined; readonly preserveConsecutiveUppercase?: boolean | undefined; readonly locale?: string | false | readonly string[] | undefined; } | { readonly pascalCase?: boolean | undefined; readonly preserveConsecutiveUppercase?: boolean | undefined; readonly capitalizeAfterNumber?: boolean | undefined; readonly locale?: string | false | readonly string[] | undefined; } |
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 | >=20 |
Frequently asked questions
What are the breaking changes when upgrading camelcase from 8 to 9?
Between camelcase 8.0.0 and 9.0.0, Vigia found 0 removed exports, 1 changed signatures and 0 removed or changed class or interface members.
What became deprecated in camelcase 9?
0 exports or members are newly marked as deprecated in camelcase 9.0.0.
For agents
GET https://vigia.coredls.cloud/v1/packages/npm/camelcase/upgrade?from=8.0.0&to=9.0.0