chore: [FFM-6891]: Update JS SDK and caching docs (#7)

Author: knagurski

README.md

@@ -108,9 +108,10 @@ The React Client SDK's asynchronous mode allows this by passing the optional `as
 ## Caching evaluations
 
 In practice flags rarely change and so it can be useful to cache the last received evaluations from the server to allow
-your application to get started as fast as possible. Setting the `cache` option as `true` will allow the SDK to store
-its evaluations to `localStorage` and retrieve at startup. This lets the SDK get started near instantly and begin
-serving flags, while it carries on authenticating and fetching up-to-date evaluations from the server behind the scenes.
+your application to get started as fast as possible. Setting the `cache` option as `true` or as an object (see interface
+below) will allow the SDK to store its evaluations to `localStorage` and retrieve at startup. This lets the SDK get
+started near instantly and begin serving flags, while it carries on authenticating and fetching up-to-date evaluations
+from the server behind the scenes.
 
 ```typescript jsx
 <FFContextProvider
@@ -127,6 +128,14 @@ serving flags, while it carries on authenticating and fetching up-to-date evalua
 </FFContextProvider>
 ```
 
+The `cache` option can also be passed as an object with the following options.
+
+```typescript
+export interface CacheOptions {
+  ttl?: number // maximum age of stored cache, in ms, before it is considered stale
+}
+```
+
 ## API
 
 ### `FFContextProvider`

examples/get-started/package-lock.json

@@ -21,7 +21,7 @@
     "react": ">=16.7.0"
   },
   "dependencies": {
-    "@harnessio/ff-javascript-client-sdk": "^1.9.1",
+    "@harnessio/ff-javascript-client-sdk": "^1.10.0",
     "lodash.omit": "^4.5.0"
   },
   "devDependencies": {