fix: react 18 Strict mode issues

The one behavioral change made is that The Router component will no longer `dispose` of the farce navigation subscription on unmount. This never was correct to do in the first place since remounting would not re subscribe. If you need to tear down the farce protocol you can dispatch dispose manually

src/createBaseRouter.js

@@ -41,8 +41,6 @@ export default function createBaseRouter({
         element: initialRenderArgs ? render(initialRenderArgs) : null,
       };
 
-      this.mounted = true;
-
       this.lastIteration = 0;
       this.pendingResolvedMatch = false;
 
@@ -60,6 +58,7 @@ export default function createBaseRouter({
     //  about having to pass around nextProps.
 
     componentDidMount() {
+      this.mounted = true;
       if (!this.props.initialRenderArgs) {
         this.resolveMatch();
       }

src/createFarceRouter.js

@@ -1,11 +1,5 @@
 import useIsomorphicEffect from '@restart/hooks/useIsomorphicEffect';
-import FarceActions from 'farce/Actions';
-import React, {
-  forwardRef,
-  useEffect,
-  useImperativeHandle,
-  useState,
-} from 'react';
+import React, { forwardRef, useImperativeHandle, useState } from 'react';
 
 import createBaseRouter from './createBaseRouter';
 import createFarceStore from './createFarceStore';
@@ -48,17 +42,12 @@ export default function createFarceRouter({
       });
     }, []);
 
-    useEffect(() => {
-      return () => {
-        // eslint-disable-next-line react-hooks/exhaustive-deps
-        store.dispatch(FarceActions.dispose());
-      };
-    }, []);
-
     useImperativeHandle(ref, () => store, []);
 
     return <Router {...props} {...state} store={store} />;
   });
+
   FarceRouter.displayName = 'FarceRouter';
+
   return FarceRouter;
 }