Upgrading clsx from 1.x to 2.x
Comparison of the public API of clsx 1.2.1 and 2.1.1, 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 | 1 |
| Removed class or interface members | 0 |
| Changed class or interface members | 0 |
| Newly deprecated | 0 |
| Requirement changes (engines, peer dependencies) | 0 |
| New exports | 0 |
Removed exports
| import | export | kind | Before |
|---|---|---|---|
clsx | default | function | (...inputs: ClassValue[]): string |
Changed signatures
| export | Before | After |
|---|---|---|
clsx · ClassValue | string | number | boolean | ClassArray | ClassDictionary | null | undefined | string | number | bigint | boolean | ClassArray | ClassDictionary | null | undefined |
Removed class or interface members
None detected.
Changed class or interface members
None detected.
Newly deprecated
None detected.
Requirement changes (engines, peer dependencies)
None detected.
Frequently asked questions
What are the breaking changes when upgrading clsx from 1 to 2?
Between clsx 1.2.1 and 2.1.1, Vigia found 1 removed exports, 1 changed signatures and 0 removed or changed class or interface members.
What became deprecated in clsx 2?
0 exports or members are newly marked as deprecated in clsx 2.1.1.
For agents
GET https://vigia.coredls.cloud/v1/packages/npm/clsx/upgrade?from=1.2.1&to=2.1.1