diff --git a/compiled/facebook-www/REVISION b/compiled/facebook-www/REVISION
index a718a0b97f612..fdea8651e78c2 100644
--- a/compiled/facebook-www/REVISION
+++ b/compiled/facebook-www/REVISION
@@ -1 +1 @@
-472854820bfd0058dfc85524051171c7b7c998c1
+2bc7d336ae7db689699baeb1fffc2c03d8753ffe
diff --git a/compiled/facebook-www/React-dev.classic.js b/compiled/facebook-www/React-dev.classic.js
index 49123312e4be0..3c21449fdd357 100644
--- a/compiled/facebook-www/React-dev.classic.js
+++ b/compiled/facebook-www/React-dev.classic.js
@@ -24,7 +24,7 @@ if (__DEV__) {
     ) {
       __REACT_DEVTOOLS_GLOBAL_HOOK__.registerInternalModuleStart(new Error());
     }
-    var ReactVersion = "18.3.0-www-classic-82bfc644";
+    var ReactVersion = "18.3.0-www-classic-14d23768";
 
     // ATTENTION
     // When adding new symbols to this file,
@@ -2776,22 +2776,24 @@ if (__DEV__) {
     }
 
     function cache(fn) {
-      // On the client (i.e. not a Server Components environment) `cache` has
-      // no caching behavior. We just return the function as-is.
-      //
-      // We intend to implement client caching in a future major release. In the
-      // meantime, it's only exposed as an API so that Shared Components can use
-      // per-request caching on the server without breaking on the client. But it
-      // does mean they need to be aware of the behavioral difference.
-      //
-      // The rest of the behavior is the same as the server implementation — it
-      // returns a new reference, extra properties like `displayName` are not
-      // preserved, the length of the new function is 0, etc. That way apps can't
-      // accidentally depend on those details.
-      return function () {
-        // $FlowFixMe[incompatible-call]: We don't want to use rest arguments since we transpile the code.
-        return fn.apply(null, arguments);
-      };
+      {
+        // On the client (i.e. not a Server Components environment) `cache` has
+        // no caching behavior. We just return the function as-is.
+        //
+        // We intend to implement client caching in a future major release. In the
+        // meantime, it's only exposed as an API so that Shared Components can use
+        // per-request caching on the server without breaking on the client. But it
+        // does mean they need to be aware of the behavioral difference.
+        //
+        // The rest of the behavior is the same as the server implementation — it
+        // returns a new reference, extra properties like `displayName` are not
+        // preserved, the length of the new function is 0, etc. That way apps can't
+        // accidentally depend on those details.
+        return function () {
+          // $FlowFixMe[incompatible-call]: We don't want to use rest arguments since we transpile the code.
+          return fn.apply(null, arguments);
+        };
+      }
     }
 
     function resolveDispatcher() {
diff --git a/compiled/facebook-www/React-dev.modern.js b/compiled/facebook-www/React-dev.modern.js
index f840e7a3196db..e92d357c40156 100644
--- a/compiled/facebook-www/React-dev.modern.js
+++ b/compiled/facebook-www/React-dev.modern.js
@@ -24,7 +24,7 @@ if (__DEV__) {
     ) {
       __REACT_DEVTOOLS_GLOBAL_HOOK__.registerInternalModuleStart(new Error());
     }
-    var ReactVersion = "18.3.0-www-modern-00e8e94b";
+    var ReactVersion = "18.3.0-www-modern-7437533c";
 
     // ATTENTION
     // When adding new symbols to this file,
@@ -2741,22 +2741,24 @@ if (__DEV__) {
     }
 
     function cache(fn) {
-      // On the client (i.e. not a Server Components environment) `cache` has
-      // no caching behavior. We just return the function as-is.
-      //
-      // We intend to implement client caching in a future major release. In the
-      // meantime, it's only exposed as an API so that Shared Components can use
-      // per-request caching on the server without breaking on the client. But it
-      // does mean they need to be aware of the behavioral difference.
-      //
-      // The rest of the behavior is the same as the server implementation — it
-      // returns a new reference, extra properties like `displayName` are not
-      // preserved, the length of the new function is 0, etc. That way apps can't
-      // accidentally depend on those details.
-      return function () {
-        // $FlowFixMe[incompatible-call]: We don't want to use rest arguments since we transpile the code.
-        return fn.apply(null, arguments);
-      };
+      {
+        // On the client (i.e. not a Server Components environment) `cache` has
+        // no caching behavior. We just return the function as-is.
+        //
+        // We intend to implement client caching in a future major release. In the
+        // meantime, it's only exposed as an API so that Shared Components can use
+        // per-request caching on the server without breaking on the client. But it
+        // does mean they need to be aware of the behavioral difference.
+        //
+        // The rest of the behavior is the same as the server implementation — it
+        // returns a new reference, extra properties like `displayName` are not
+        // preserved, the length of the new function is 0, etc. That way apps can't
+        // accidentally depend on those details.
+        return function () {
+          // $FlowFixMe[incompatible-call]: We don't want to use rest arguments since we transpile the code.
+          return fn.apply(null, arguments);
+        };
+      }
     }
 
     function resolveDispatcher() {