@clr/ui - npm Package Compare versions
Comparing version 15.11.0 to 16.0.0-beta.1
@@ -14,3 +14,6 @@ { | ||
| }, | ||
| "version": "15.11.0" | ||
| "peerDependencies": { | ||
| "@cds/core": "^6.6.0" | ||
| }, | ||
| "version": "16.0.0-beta.1" | ||
| } |
@@ -9,3 +9,3 @@ ## Installing Clarity UI [](https://badge.fury.io/js/%40clr%2Fui) | ||
| 2. Include clr-ui.min.css in your HTML file: | ||
| 2. Include clr-ui.min.css in your HTML file and add the cds-theme attribute to your body tag: | ||
@@ -16,2 +16,30 @@ ``` | ||
| 3. Write your HTML with the Clarity CSS class names and markup. | ||
| 3. Add the `cds-theme="light"` (or `cds-theme="dark"` for dark theme) to the body tag: | ||
| ``` | ||
| <body cds-theme"light"> | ||
| ``` | ||
| 4. Write your HTML with the Clarity CSS class names and markup. | ||
| ## Legacy Styles (pre-v16) | ||
| Clarity recently introduced the Clarity Design System within the @cds/core library. As of v16, the Clarity team has | ||
| migrated that system and styles to this and the @clr/angular package. This change came with UI changes that teams | ||
| may not be prepared to make without proper planning, so the Clarity team has retained the existing styles but that | ||
| has been moved to a legacy file that will be removed in v17 (~Jan-Feb/2024). To use those legacy styles, reference | ||
| the file from its new location. | ||
| ``` | ||
| <link rel="stylesheet" href="path/to/node_modules/@clr/ui/legacy-clr-ui.min.css"> | ||
| <!-- OR --> | ||
| <link rel="stylesheet" href="path/to/node_modules/@clr/ui/legacy-clr-ui-dark.min.css"> | ||
| ``` | ||
| ## Versioning | ||
| The version of this library is aligned to the version of @clr/angular, and does not independently follow semantic | ||
| versioning. While we strive to only introduce breaking changes in major versions, we may at times need to introduce | ||
| a breaking change in a minor version in order to maintain alignment with the @clr/angular library. For projects that | ||
| choose to use this package, we recommend pinning your project to a specific path version and treating each upgrade | ||
| as a potentially breaking change. |
Sorry, the diff of this file is not supported yet
Sorry, the diff of this file is not supported yet
Sorry, the diff of this file is not supported yet
Sorry, the diff of this file is not supported yet
Sorry, the diff of this file is not supported yet
Sorry, the diff of this file is not supported yet
Sorry, the diff of this file is not supported yet
Sorry, the diff of this file is not supported yet
Sorry, the diff of this file is not supported yet
Sorry, the diff of this file is not supported yet
Sorry, the diff of this file is not supported yet
Sorry, the diff of this file is not supported yet
Sorry, the diff of this file is not supported yet
Sorry, the diff of this file is not supported yet
Sorry, the diff of this file is not supported yet
Sorry, the diff of this file is not supported yet
Sorry, the diff of this file is not supported yet
Sorry, the diff of this file is not supported yet
Sorry, the diff of this file is not supported yet
Sorry, the diff of this file is not supported yet
Sorry, the diff of this file is not supported yet
Sorry, the diff of this file is not supported yet
Sorry, the diff of this file is not supported yet
Sorry, the diff of this file is not supported yet
Sorry, the diff of this file is not supported yet
Sorry, the diff of this file is not supported yet
Sorry, the diff of this file is not supported yet
Sorry, the diff of this file is not supported yet
Sorry, the diff of this file is not supported yet
Sorry, the diff of this file is not supported yet
Sorry, the diff of this file is not supported yet
Sorry, the diff of this file is not supported yet
Sorry, the diff of this file is too big to display
New alerts
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
Major refactor
Supply chain riskPackage has recently undergone a major refactor. It may be unstable or indicate significant internal changes. Use caution when updating to versions that include significant changes.
Found 1 instance in 1 package
No v1
QualityPackage is not semver >=1. This means it is not stable and does not support ^ ranges.
Found 1 instance in 1 package
Fixed alerts
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
Improved metrics
- Total package byte prevSize
- increased by42.78%
10119306
- Number of package files
- increased by2.45%
167
- Lines of code
- increased by80.18%
81128
- Number of lines in readme file
- increased by175%
44
Worsened metrics
- Dependency count
- increased byInfinity%
1
- Number of low quality alerts
- increased byInfinity%
1
- Number of medium supply chain risk alerts
- increased byInfinity%
1