Fix: use Object.is for dependency comparison to handle NaN correctly

Previously, the React Compiler generated code using !== for dependency
comparison, which doesn't match React's Object.is semantics. This caused
NaN in dependency arrays to always trigger re-evaluation since
NaN !== NaN is true, but Object.is(NaN, NaN) is true.

This fix changes the generated code to use !Object.is() for dependency
comparison, which correctly handles NaN and other edge cases like -0.

Fixes #35854

Author: MorikawaSouma

compiler/packages/babel-plugin-react-compiler/src/ReactiveScopes/CodegenReactiveFunction.ts

@@ -574,14 +574,22 @@ function codegenReactiveScope(
 
   for (const dep of [...scope.dependencies].sort(compareScopeDependency)) {
     const index = cx.nextCacheIndex;
-    const comparison = t.binaryExpression(
-      '!==',
-      t.memberExpression(
-        t.identifier(cx.synthesizeName('$')),
-        t.numericLiteral(index),
-        true,
+    // Use Object.is for dependency comparison to match React's equality semantics.
+    // This correctly handles NaN (NaN !== NaN is true, but Object.is(NaN, NaN) is true).
+    // We negate Object.is since we want to detect changes (inequality).
+    const comparison = t.unaryExpression(
+      '!',
+      t.callExpression(
+        t.memberExpression(t.identifier('Object'), t.identifier('is')),
+        [
+          t.memberExpression(
+            t.identifier(cx.synthesizeName('$')),
+            t.numericLiteral(index),
+            true,
+          ),
+          codegenDependency(cx, dep),
+        ],
       ),
-      codegenDependency(cx, dep),
     );
     changeExpressions.push(comparison);
     /*