Gathering detailed insights and metrics for @progress/kendo-theme-fluent
Gathering detailed insights and metrics for @progress/kendo-theme-fluent
Gathering detailed insights and metrics for @progress/kendo-theme-fluent
Gathering detailed insights and metrics for @progress/kendo-theme-fluent
npm install @progress/kendo-theme-fluent
Module System
Min. Node Version
Typescript Support
Node Version
NPM Version
149 Stars
10,221 Commits
71 Forks
55 Watching
54 Branches
168 Contributors
Updated on 27 Nov 2024
HTML (58.66%)
SCSS (28.13%)
TypeScript (12.77%)
JavaScript (0.31%)
Shell (0.09%)
Nunjucks (0.04%)
CSS (0.02%)
Cumulative downloads
Total Downloads
Last day
-39.2%
1,073
Compared to previous day
Last week
-42.8%
6,194
Compared to previous week
Last month
13.9%
38,037
Compared to previous month
Last year
118.4%
296,456
Compared to previous year
kendo-themes
is a lerna managed monorepo project for all Kendo UI themes that are used across the Kendo UI suites and Telerik UI for Blazor. The themes are built with sass using scss syntax. The syntax is compatible with both node-sass
and dart-sass
, as we currently do not use the sass module system. Browser-specific properties are generated at build-time through PostCSS autoprefixer.
npm ci
to install dependencies.To run it, execute npm start
and navigate to http://localhost:3000/
The following npm commands are available for building the themes:
npm run sass
.npm run sass:swatches
.There are additional commands, which can be found in package.json
and gulpfile.js
.
Inside each theme source directory, there is a per-component directory containing the respective styles.
Note: we mostly have aptly named direcotries, so they match component names. In few cases, however, we chose different names. For example, multicolumncombobox
is a mouthful, so its directory is dropdowngrid
.
Each component consists of index
file that is the entry points for component styles. Inside, we import core
files, all dependencies (for example, datepicker needs calendar) and the components layout
(metrics) and theme
(appearance) files.
Note: We list all dependencies is because we want components to be compiled standalone without the developer needing to know which component depends on which other component. However, recursive importing creates exponentially large dist files, unles handled.
To workaround this limitation, we use a mixin --
import-once
-- which takes care to output only once!
During development, the scss files are linted on every commit
and built on every push
command.
Changes in develop
branch release a new package version every monday in the dev
channel and in (version)-dev.(integer)
format. To install the latest development version of a given theme, run npm install (themename)@dev
-- for example, npm install @progress/kendo-theme-default@dev
.
Stable channel is released manually trough a github action.
To guard against regressions and make pull request reviews easier, the CI build makes screenshots of the sample pages in packages/html/src/[component]/tests/*.html
. This happens automatically for all feature branches. The sample pages contain static HTML that is the recommended rendering for components that use the theme.
To generate screenshots for a specific theme:
npm run sass
npm run create-screenshots <theme>
, substituting <theme>
with a theme name.These steps will create new screenshots in tests/_output
. Note that due to platform differences, all of the files will be marked as changed.
To avoid hosting-related issues in projects that use the themes, the resources are embedded by encoding them in the output CSS. For more details, refer to this issue.
To embed the latest resources:
npm run embed-assets
task. The task generates a file with the same name which registers a Base64-encoded version in the $data-uris
SCSS map. For example, the foo.woff
font file will be encoded in a foo.scss
file which can later be imported through @import './font/foo';
.map-get( $data-uris, 'foo.woff' )
. For example:1$web-font-uri: map-get( $data-uris, 'WebComponentsIcons.woff' ); 2 3@font-face { 4 font-family: 'WebComponentsIcons'; 5 src: url( $web-font-uri ) format( "woff" ); 6}
The available variables for customizing each theme are listed in the article on customization for each theme (docs/customization.md
) The file is generated from the SCSS source files by running the npm run docs
command.
To document a variable, use triple-slash comments (///
) before its definition.
1/// Variable description 2$foo: 42 !default;
To group variables, use the @group
directive.
1/// Variable description 2/// @group random 3$foo: 42 !default; 4 5/// Another variable description 6/// @group random 7$bar: 1024 !default;
To change the layout or the front meter of the generated help topic, change the docs/_templates/customization.md.njk
source file.
This package is part of the following suites:
All available Kendo UI commercial licenses may be obtained at http://www.telerik.com/purchase/kendo-ui.
If you do not own a commercial license, the usage of this software shall be governed by the Apache License, Version 2.0.
Copyright © 2021 Progress Software Corporation and/or one of its subsidiaries or affiliates. All rights reserved.
Progress, Telerik, and certain product names used herein are trademarks or registered trademarks of Progress Software Corporation and/or one of its subsidiaries or affiliates in the U.S. and/or other countries.
No vulnerabilities found.
Reason
no dangerous workflow patterns detected
Reason
30 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 10
Reason
packaging workflow detected
Details
Reason
no binaries found in the repo
Reason
Found 11/15 approved changesets -- score normalized to 7
Reason
dependency not pinned by hash detected -- score normalized to 4
Details
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
license file not detected
Details
Reason
detected GitHub workflow tokens with excessive permissions
Details
Reason
project is not fuzzed
Details
Reason
security policy file not detected
Details
Reason
SAST tool is not run on all commits -- score normalized to 0
Details
Reason
13 existing vulnerabilities detected
Details
Score
Last Scanned on 2024-11-18
The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.
Learn More