@vaadin/vaadin-progress-bar - npm Package Compare versions

Comparing version 1.1.0 to 1.1.1

package.json

@@ -14,3 +14,3 @@ {
   "name": "@vaadin/vaadin-progress-bar",
-  "version": "1.1.0",
+  "version": "1.1.1",
   "main": "vaadin-progress-bar.js",
@@ -22,2 +22,7 @@ "author": "Vaadin Ltd",
   },
+  "files": [
+    "vaadin-*.js",
+    "src",
+    "theme"
+  ],
   "resolutions": {
@@ -37,8 +42,7 @@ "inherits": "2.0.3",
   "devDependencies": {
-    "@polymer/iron-component-page": "^3.0.0-pre.18",
-    "@polymer/iron-demo-helpers": "^3.0.0-pre.18",
+    "@polymer/iron-component-page": "^4.0.0",
     "@webcomponents/webcomponentsjs": "^2.0.0",
     "wct-browser-legacy": "^1.0.1",
-    "@vaadin/vaadin-demo-helpers": "^2.0.1"
+    "@vaadin/vaadin-demo-helpers": "^3.0.0"
   }
 }

README.md

@@ -96,16 +96,16 @@ [![npm version](https://badgen.net/npm/v/@vaadin/vaadin-progress-bar)](https://www.npmjs.com/package/@vaadin/vaadin-progress-bar)
 
-## Running demos and tests in browser
+## Running demos and tests in a browser
 
 1. Fork the `vaadin-progress-bar` repository and clone it locally.
 
-1. Make sure you have [npm](https://www.npmjs.com/) installed.
+1. Make sure you have [npm](https://www.npmjs.com/) and [Bower](https://bower.io) installed.
 
 1. When in the `vaadin-progress-bar` directory, run `npm install` and then `bower install` to install dependencies.
 
-1. Run `polymer serve --open`, browser will automatically open the component API documentation.
+1. Run `npm start`, browser will automatically open the component API documentation.
 
 1. You can also open demo or in-browser tests by adding **demo** or **test** to the URL, for example:
 
-  - http://127.0.0.1:8080/components/vaadin-progress-bar/demo
-  - http://127.0.0.1:8080/components/vaadin-progress-bar/test
+  - http://127.0.0.1:3000/components/vaadin-progress-bar/demo
+  - http://127.0.0.1:3000/components/vaadin-progress-bar/test
 
@@ -120,5 +120,10 @@
 
-We are using [ESLint](http://eslint.org/) for linting JavaScript code. You can check if your code is following our standards by running `gulp lint`, which will automatically lint all `.js` files as well as JavaScript snippets inside `.html` files.
+We are using [ESLint](http://eslint.org/) for linting JavaScript code. You can check if your code is following our standards by running `npm run lint`, which will automatically lint all `.js` files as well as JavaScript snippets inside `.html` files.
 
 
+## Big Thanks
+
+Cross-browser Testing Platform and Open Source <3 Provided by [Sauce Labs](https://saucelabs.com).
+
+
 ## Contributing
@@ -125,0 +130,0 @@

src/vaadin-progress-bar.js

@@ -85,3 +85,3 @@ /**
   static get version() {
-    return '1.1.0';
+    return '1.1.1';
   }
@@ -88,0 +88,0 @@ }

theme/lumo/vaadin-progress-bar-styles.js

@@ -6,5 +6,5 @@ import '@polymer/polymer/lib/elements/custom-style.js';
 import '@vaadin/vaadin-lumo-styles/style.js';
-const $_documentContainer = document.createElement('template');
+import { html } from '@polymer/polymer/lib/utils/html-tag.js';
 
-$_documentContainer.innerHTML = `<dom-module id="lumo-progress-bar" theme-for="vaadin-progress-bar">
+const $_documentContainer = html`<dom-module id="lumo-progress-bar" theme-for="vaadin-progress-bar">
   <template>
@@ -144,7 +144,1 @@ <style>
 /* Safari fails to declare animations for pseudo elements inside a shadow DOM */
-/*
-  FIXME(polymer-modulizer): the above comments were extracted
-  from HTML and may be out of place here. Review them and
-  then delete this comment!
-*/
-;

theme/material/vaadin-progress-bar-styles.js

 import '@vaadin/vaadin-material-styles/color.js';
-const $_documentContainer = document.createElement('template');
+import { html } from '@polymer/polymer/lib/utils/html-tag.js';
 
-$_documentContainer.innerHTML = `<dom-module id="material-progress-bar" theme-for="vaadin-progress-bar">
+const $_documentContainer = html`<dom-module id="material-progress-bar" theme-for="vaadin-progress-bar">
   <template>
@@ -6,0 +6,0 @@ <style>

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

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

Improved metrics

Dev dependency count

4

decreased by-20%

Number of lines in readme file

137

increased by3.79%

Worsened metrics

Total package byte prevSize

29449

decreased by-12.48%

Number of package files

10

decreased by-16.67%

Lines of code

368

decreased by-2.39%

No dependency changes