chore: bump version to 2.2.0 and update CHANGELOG to reflect removal …

…of next.js useRouter support

CHANGELOG.md

@@ -1,5 +1,11 @@
 # react-content-manager
 
+## 2.2.0
+
+### Minor Changes
+
+- Removed support to execute useRouter from next.js, because it blocked way to work with Vite and forces developer to always refresh RSC (react server components). If you want to still have this feature you can pass it inside onSuccess/onFailure as params of saveChange
+
 ## 2.1.5
 
 ### Patch Changes

package.json

@@ -1,6 +1,6 @@
 {
   "name": "react-content-manager",
-  "version": "2.1.5",
+  "version": "2.2.0",
   "description": "enable editable components in your react app",
   "keywords": [
     "react",

src/context/CMConfigContext.tsx

@@ -38,10 +38,6 @@ export const CMConfigContextProvider = (
   const [isSaving, setIsSaving] = useState(false);
   const [api, contextHolder] = notification.useNotification();
 
-  let nextRouter = null;
-  // @TODO remove it or load it a way that it will support Vite
-  nextRouter = require("next/navigation").useRouter();
-
   const setModeHandler = useCallback(
     (mode: "edit" | "view") => {
       setMode(mode);
@@ -61,9 +57,6 @@ export const CMConfigContextProvider = (
         setIsSaving(true);
         const persister = getPersister();
         await persister(configId, componentId, props);
-        if (nextRouter) {
-          nextRouter.refresh();
-        }
         if (onSuccess) {
           onSuccess();
         } else {
@@ -88,7 +81,7 @@ export const CMConfigContextProvider = (
         setIsSaving(false);
       }
     },
-    [nextRouter],
+    [],
   );
 
   const contextValue: CMConfigContextProps = {