@webqit/webflo 0.11.8 → 0.11.9

package/README.md

@@ -1265,7 +1265,7 @@ Unless disabled in config, it is factored-in at build time for the application c
 ```json
 { "spa_navigation": true }
 ```
-<details>
+</details>
 
 ##### SPA State
 
@@ -1413,7 +1413,7 @@ Webflo client-side applications are intended to provide an app-like-first experi
 ```json
 { "enable_service_worker": true }
 ```
-<details>
+</details>
 
 ##### Fetching Strategy
 
@@ -1433,7 +1433,7 @@ Webflo client-side applications are intended to provide an app-like-first experi
     ```json
     { "network_first_urls": [ "/logo.png" ] }
     ```
-    <details>
+    </details>
 
 + **Cache First** - This strategy tells the Service Worker to always attempt fetching from the cache first for given resources, before fetching from the network. After serving a cached response, or where not found in cache, a network fetch happens and a copy of the response is saved to the cache for next time. (This is good for resources that do not critially need to be fresh to the user.) When not the default strategy, a list of specific URLs that should be fetched this way can be configured.
     
@@ -1451,7 +1451,7 @@ Webflo client-side applications are intended to provide an app-like-first experi
     ```json
     { "cache_first_urls": [ "/logo.png" ] }
     ```
-    <details>
+    </details>
 
 + **Network Only** - This strategy tells the Service Worker to always fetch given resources from the network only. They are simply not available when offline. (This is good for resources that critially need to be fresh to the user.) When not the default strategy, a list of specific URLs that should be fetched this way can be configured.
     
@@ -1469,7 +1469,7 @@ Webflo client-side applications are intended to provide an app-like-first experi
     ```json
     { "network_only_urls": [ "/logo.png" ] }
     ```
-    <details>
+    </details>
 
 + **Cache Only** - This strategy tells the Service Worker to always fetch given resources from the cache only. (This is good for resources that do not change often.) When not the default strategy, a list of specific URLs that should be fetched this way can be configured. The listed resources are pre-cached ahead of when they'll be needed - and are served from the cache each time. (Pre-caching happens on the one-time `install` event of the Service Worker.)
 
@@ -1487,7 +1487,7 @@ Webflo client-side applications are intended to provide an app-like-first experi
     ```json
     { "cache_only_urls": [ "/logo.png" ] }
     ```
-    <details>
+    </details>
 
 In all cases above, the convention for specifying URLs for a strategy accepts [URL patterns](https://developer.mozilla.org/en-US/docs/Web/API/URLPattern) - against which URLs can be matched on the fly. For example, to place all files in an `/image` directory (and subdirectories) on the *Cache First* strategy, the pattern `/image/*` can be used. To place all `.svg` files in an `/icons` directory (including subdirectories) on the *Cache Only* strategy, the pattern `/icons/*.svg` can be used. (Specifically for the *Cache Only* strategy, patterns are resolved at Service Worker build-time, and each pattern must match, at least, a file.)
 
@@ -1729,7 +1729,7 @@ Webflo natively supports OOHTML in full! But it is also possible to switch this
 ```
 
 *Values: `full`, `namespacing`, `scripting`, `templating`, `none` - See [details at OOHTML SSR](https://github.com/webqit/oohtml-ssr#options)*
-<details>
+</details>
 
 
 ### OOHTML SSR

package/package.json

@@ -12,7 +12,7 @@
     "vanila-javascript"
   ],
   "homepage": "https://webqit.io/tooling/webflo",
-  "version": "0.11.8",
+  "version": "0.11.9",
   "license": "MIT",
   "repository": {
     "type": "git",