fix: Remove warnings from useDeepCompareEffect (fixes #755)

Removes console.warn statements that were causing frustration for valid
use cases where dependencies could be either undefined or an object.

The hook works correctly regardless of dependency types (primitives,
objects, or mixed), so the warnings were unnecessary and frustrating
for developers with valid use cases.

This directly addresses issue #755 where users reported frustration
with warnings appearing in local development environments when using
the hook with dependencies that could be undefined or objects.

Author: Kamal Sai Devarapalli

docs/useDeepCompareEffect.md

@@ -23,6 +23,15 @@ const Demo = () => {
 };
 ```
 
+## Valid Use Cases
+
+This hook is particularly useful when:
+- Dependencies could be either `undefined` or an object that you'd like to be deep-compared
+- You need to compare complex objects by value rather than reference
+- Dependencies may include primitive values mixed with objects
+
+The hook works correctly with any dependency array, including primitives, objects, or mixed types.
+
 ## Reference
 
 ```ts

src/useDeepCompareEffect.ts

@@ -2,23 +2,7 @@ import { DependencyList, EffectCallback } from 'react';
 import useCustomCompareEffect from './useCustomCompareEffect';
 import isDeepEqual from './misc/isDeepEqual';
 
-const isPrimitive = (val: any) => val !== Object(val);
-
 const useDeepCompareEffect = (effect: EffectCallback, deps: DependencyList) => {
-  if (process.env.NODE_ENV !== 'production') {
-    if (!(deps instanceof Array) || !deps.length) {
-      console.warn(
-        '`useDeepCompareEffect` should not be used with no dependencies. Use React.useEffect instead.'
-      );
-    }
-
-    if (deps.every(isPrimitive)) {
-      console.warn(
-        '`useDeepCompareEffect` should not be used with dependencies that are all primitive values. Use React.useEffect instead.'
-      );
-    }
-  }
-
   useCustomCompareEffect(effect, deps, isDeepEqual);
 };