.prettierignore

@@ -0,0 +1,7 @@
+node_modules
+tap-snapshots
+coverage
+.nyc_output
+bench-lru
+.github
+scripts

CHANGELOG.md

@@ -1,9 +1,19 @@
 # cringe lorg
 
+## 7.10.0
+
+* Add `noDeleteOnFetchRejection` option, to suppress behavior
+  where a failed `fetch` will delete a previous stale value.
+* Ship types along with the package, rather than relying on
+  out of date types coming from DefinitelyTyped.
+
 ## 7.9.0
 
 * Better AbortController polyfill, supporting
   `signal.addEventListener('abort')` and `signal.onabort`.
+* (7.9.1) Drop item from cache instead of crashing with an
+  `unhandledRejection` when the `fetchMethod` throws an error or
+  returns a rejected Promise.
 
 ## 7.8.0
 

README.md

@@ -164,6 +164,23 @@ value is resolved.  For example, a DNS cache may update the TTL
 based on the value returned from a remote DNS server by changing
 `options.ttl` in the `fetchMethod`.
 
+### `noDeleteOnFetchRejection`
+
+If a `fetchMethod` throws an error or returns a rejected promise,
+then by default, any existing stale value will be removed from
+the cache.
+
+If `noDeleteOnFetchRejection` is set to `true`, then this
+behavior is suppressed, and the stale value remains in the cache
+in the case of a rejected `fetchMethod`.
+
+This is important in cases where a `fetchMethod` is _only_ called
+as a background update while the stale value is returned, when
+`allowStale` is used.
+
+This may be set in calls to `fetch()`, or defaulted on the
+constructor.
+
 ### `dispose`
 
 Function that is called on items when they are dropped from the