@ngx-pwa/ngsw-schema - npm Package Compare versions

Comparing version 1.0.0 to 1.0.1

package.json

 {
   "name": "@ngx-pwa/ngsw-schema",
-  "version": "1.0.0",
+  "version": "1.0.1",
   "description": "JSON schema for Angular service worker configuration file (ngsw-config.json)",
@@ -5,0 +5,0 @@ "author": "Cyrille Tuzi",

README.md

@@ -20,5 +20,4 @@ # JSON schema for Angular service worker configuration file (`ngsw-config.json`)
 
-Of course, I have proposed it as [a PR in Angular repo](https://github.com/angular/angular/pull/27859),
-and it has already been reviewed by the Angular team, but since then,
-no news about merging. As I'm tired of fighting, I'm proposing this as an external contribution for now.
+I proposed [a PR in Angular repo](https://github.com/angular/angular/pull/27859).
+While waiting for merge, I'm proposing this as an external contribution.
 
@@ -29,3 +28,3 @@ ## By the same author
 - [@ngx-pwa/local-storage](https://github.com/cyrilletuzi/angular-async-local-storage): 1st Angular library for local storage
-- Library [@ngx-pwa/offline](https://github.com/cyrilletuzi/ngx-pwa-offline)
+- Other Angular library: [@ngx-pwa/offline](https://github.com/cyrilletuzi/ngx-pwa-offline)
 - Popular [Angular posts on Medium](https://medium.com/@cyrilletuzi)
@@ -32,0 +31,0 @@ - Follow updates of this lib on [Twitter](https://twitter.com/cyrilletuzi)

schema.json

 {
-  "$schema": "http://json-schema.org/draft-07/schema",
+  "$schema": "https://json-schema.org/draft-07/schema",
   "type": "object",
@@ -60,7 +60,6 @@ "properties": {
                 "uniqueItems": true
-              },
-              "additionalProperties": false
-            }
-          },
-          "additionalProperties": false
+              }
+            },
+            "additionalProperties": false
+          }
         },
@@ -70,3 +69,4 @@ "required": [
           "resources"
-        ]
+        ],
+        "additionalProperties": false
       }
@@ -120,4 +120,3 @@ },
                 "description": "The Angular service worker can use either of two caching strategies for data resources. 'performance', the default, optimizes for responses that are as fast as possible. If a resource exists in the cache, the cached version is used. This allows for some staleness, depending on the 'maxAge', in exchange for better performance. This is suitable for resources that don't change often; for example, user avatar images. 'freshness' optimizes for currency of data, preferentially fetching requested data from the network. Only if the network times out, according to 'timeout', does the request fall back to the cache. This is useful for resources that change frequently; for example, account balances."
-              },
-              "additionalProperties": false
+              }
             },
@@ -127,5 +126,5 @@ "required": [
               "maxAge"
-            ]
-          },
-          "additionalProperties": false
+            ],
+            "additionalProperties": false
+          }
         },
@@ -136,3 +135,4 @@ "required": [
           "cacheConfig"
-        ]
+        ],
+        "additionalProperties": false
       }
@@ -139,0 +139,0 @@ },

No alert changes

Worsened metrics

Total package byte prevSize

13427

decreased by-0.86%

Number of lines in readme file

55

decreased by-1.79%

No dependency changes