@progress/kendo-theme-default - npm Package Compare versions

Comparing version 1.33.0 to 2.0.0

package.json

 {
   "name": "@progress/kendo-theme-default",
   "description": "SASS resources for the default Kendo UI theme",
-  "version": "1.33.0",
+  "version": "2.0.0",
   "keywords": [
@@ -13,2 +13,3 @@ "Kendo UI",
     "build": "webpack --optimize-minimize --bail",
+    "watch": "webpack --watch",
     "embed-assets": "node build/embed-assets.js",
@@ -18,3 +19,3 @@ "test": "npm run lint && npm run build",
   },
-  "main": "styles/packages/all.scss",
+  "main": "dist.css",
   "author": "Progress",
@@ -33,2 +34,5 @@ "license": "Apache-2.0",
   },
+  "publishConfig": {
+    "registry": "https://registry.npm.telerik.com"
+  },
   "config": {
@@ -35,0 +39,0 @@ "commitizen": {

README.md

@@ -40,1 +40,3 @@ [![Build Status](https://travis-ci.org/telerik/kendo-theme-default.svg?branch=master)](https://travis-ci.org/telerik/kendo-theme-default)
 Upon build, browser-specific properties are generated through the [PostCSS autoprefixer](https://github.com/postcss/autoprefixer).
+
+When updating resources (images or fonts), run the `npm run embed-assets` task. This will generate a file with the same name, which registers a base64-encoded version in the `$data-uris` SCSS map. For example, the font file `foo.woff` will receive a `foo.scss` file, which can later be imported via `@import './font/foo';`. Then the base64 version can be inlined via `map-get( $data-uris, 'WebComponentsIcons.woff' )`. This is done in order to workaround problems with hosting resources when consuming the theme. See [issue #41](https://github.com/telerik/kendo-theme-default/issues/41#issuecomment-258472183) for more details.

New alerts

License Policy Violation

License

This package is not allowed per your license policy. Review the package's license to ensure compliance.

Found 1 instance in 1 package

Native code

Supply chain risk

Contains native code (e.g., compiled binaries or shared libraries). Including native code can obscure malicious behavior.

Found 1 instance in 1 package

Shell access

Supply chain risk

This module accesses the system shell. Accessing the system shell increases the risk of executing arbitrary code.

Found 1 instance in 1 package

Environment variable access

Supply chain risk

Package accesses environment variables, which may be a sign of credential stuffing or data theft.

Found 1 instance in 1 package

Filesystem access

Supply chain risk

Accesses the file system, and could potentially read sensitive data.

Found 1 instance in 1 package

Fixed alerts

License Policy Violation

License

This package is not allowed per your license policy. Review the package's license to ensure compliance.

Found 1 instance in 1 package

Native code

Supply chain risk

Contains native code (e.g., compiled binaries or shared libraries). Including native code can obscure malicious behavior.

Found 1 instance in 1 package

Improved metrics

Total package byte prevSize

807648

increased by6.5%

Number of package files

163

increased by50.93%

Lines of code

94

increased by261.54%

Number of lines in readme file

42

increased by5%

Worsened metrics

Number of low supply chain risk alerts

3

increased byInfinity%

Number of medium supply chain risk alerts

2

increased by100%

No dependency changes