linter and version bump to 0.6.6

package.json

@@ -1,6 +1,6 @@
 {
   "name": "@untra/naiveasync",
-  "version": "0.6.4",
+  "version": "0.6.6",
   "description": "An Opinionated and Painless React & Redux promise wrapper",
   "main": "./dist/src/naiveasync/index.js",
   "types": "./dist/src/naiveasync/index.d.ts",
@@ -12,7 +12,7 @@
   },
   "repository": {
     "type": "git",
-    "url": "git+https://github.com/stackhawk/naiveasync.git"
+    "url": "git+https://github.com/untra/naiveasync.git"
   },
   "homepage": "https://naiveasync.untra.io/",
   "jest": {
@@ -26,7 +26,6 @@
   "scripts": {
     "postversion": "git push && git push --tags",
     "prepublishOnly": "npm run ci && npm run defs",
-    "postpublish": "npm run deploy",
     "preversion": "npm run ci",
     "test": "npm run build && jest",
     "build": "rm -rf dist && mkdir dist && cp src/index.html dist/index.html && tsc -p build.tsconfig.json && npm run defs",

src/routes/home.tsx

@@ -196,18 +196,19 @@ const asyncOperation = (params: ParamsValue): Promise<DataValue> =>
             lifecycle to your redux store. The difference is subtle:
             <ul>
               <li>
-                use <b>.call()</b> to call the promise and reset the state of the lifecycle
-                immediately. Good for when you want the current data invalidated ASAP before any
-                data is returned.  For example:
+                use <b>.call()</b> to call the promise and reset the state of
+                the lifecycle immediately. Good for when you want the current
+                data invalidated ASAP before any data is returned. For example:
                 <i>
                   create, update, delete operations, tests and dynamic
                   operations.
                 </i>
               </li>
               <li>
-                use <b>.sync()</b> to call the promise but retain the existing state of the
-                lifecycle until data is returned.  Note that as a convenience, subsequent `sync`
-                invocations without parameters will reuse the last specified parameters.  Good for:
+                use <b>.sync()</b> to call the promise but retain the existing
+                state of the lifecycle until data is returned. Note that as a
+                convenience, subsequent `sync` invocations without parameters
+                will reuse the last specified parameters. Good for:
                 <i>
                   get, indexes, subscriptions, and searches, idempotent
                   operations
@@ -263,17 +264,18 @@ const asyncOperation = (params: ParamsValue): Promise<DataValue> =>
                 </code>{" "}
                 Action creator that triggers the associated{" "}
                 <code>AsyncOperation</code> when dispatched, passing{" "}
-                <code>params</code> into the operation. Resets its state immediately
-                when called.
+                <code>params</code> into the operation. Resets its state
+                immediately when called.
               </li>
               <li>
                 <code>
                   <strong>.sync({})</strong>
                 </code>{" "}
                 Action creator that triggers the associated `AsyncOperation`
                 when dispatched, reusing the last employed params if none are
-                provided. Does not reset data or error states until data is returned,
-                making it useful for polling / repeated "read/get" operations.
+                provided. Does not reset data or error states until data is
+                returned, making it useful for polling / repeated "read/get"
+                operations.
               </li>
               <li>
                 <code>