account for webpack

Author: RulaKhaled

packages/node/src/integrations/tracing/vercelai/index.ts

@@ -10,15 +10,20 @@ export const instrumentVercelAi = generateInstrumentOnce(INTEGRATION_NAME, () =>
 /**
  * Determines if the 'ai' package is installed and available.
  *
- * Uses require.resolve() to check for package availability without loading it.
- * This approach avoids race conditions that can occur with filesystem-based
- * detection during initialization in serverless environments (Lambda/Vercel).
+ * Uses dynamic property access to hide require.resolve from bundler static analysis.
+ * This prevents webpack from trying to resolve 'ai' at build time while
+ * still allowing runtime detection.
+ *
+ * We use this instead of modulesIntegration because in Next.js v16 with Turbopack,
+ * the modules list is empty at initialization time (race condition).
  *
  * @returns true if the 'ai' package can be resolved, false otherwise
  */
 function shouldForceIntegration(): boolean {
   try {
-    require.resolve('ai');
+    const req = require;
+    const resolve = req['resolve'];
+    resolve('ai');
     return true;
   } catch {
     return false;
@@ -36,13 +41,12 @@ const _vercelAIIntegration = ((options: VercelAiOptions = {}) => {
     },
     afterAllSetup(client) {
       // Auto-detect if we should force the integration when the 'ai' package is available
-      // Uses require.resolve() for reliable detection in all environments
+      // Uses dynamic property access for bundler-safe detection
       const shouldForce = options.force ?? shouldForceIntegration();
 
       if (shouldForce) {
         addVercelAiProcessors(client);
       } else {
-        // Lazy registration - only registers when 'ai' package is actually imported
         instrumentation?.callWhenPatched(() => addVercelAiProcessors(client));
       }
     },