fix: an issue where addMetadata calls were stripped in production m…

…ode, ensuring consistent metadata availability (e.g., `cacheOutcome`) in both development and production environments

.changeset/fluffy-starfishes-unite.md

@@ -0,0 +1,5 @@
+---
+'@urql/core': minor
+---
+
+Fixes an issue where `addMetadata` calls were stripped in production mode, ensuring consistent metadata availability (e.g., `cacheOutcome`) in both development and production environments

scripts/babel/transform-debug-target.mjs

@@ -4,19 +4,11 @@ const warningDevCheckTemplate = `
   process.env.NODE_ENV !== 'production' ? NODE : undefined
 `.trim();
 
-const noopTransformTemplate = `
-  process.env.NODE_ENV !== 'production' ? NODE : FALLBACK
-`.trim();
-
 const plugin = ({ template, types: t }) => {
   const wrapWithDevCheck = template.expression(warningDevCheckTemplate, {
     placeholderPattern: /^NODE$/,
   });
 
-  const wrapWithNoopTransform = template.expression(noopTransformTemplate, {
-    placeholderPattern: /^(NODE|FALLBACK)$/,
-  });
-
   let name = 'unknownExchange';
 
   return {
@@ -47,14 +39,6 @@ const plugin = ({ template, types: t }) => {
           }
 
           path.replaceWith(wrapWithDevCheck({ NODE: path.node }));
-        } else if (path.node.callee.name === 'addMetadata') {
-          path.node[visited] = true;
-          path.replaceWith(
-            wrapWithNoopTransform({
-              NODE: path.node,
-              FALLBACK: path.node.arguments[0],
-            })
-          );
         }
       },
     },