Initializing Humanloop SDK fails with SemVer TypeError in Cloudflare Worker #10

Activity

1. jamesbaskerville commented on Feb 19, 2025

   

   jamesbaskerville

   on Feb 19, 2025

   Last edited by jamesbaskerville

   Contributor

   More actions

   Hi @HananAlsawy, after a little digging I've found this occurs because @opentelemetry/sdk-trace-node checks against process.version, which doesn't exist in the CF Worker runtime. We'll consider supporting Cloudflare Workers better, but I can't promise anything soon.

   For now, I was able to get around this constraint by patching the globalThis and assigning a mock version to process. Hopefully unnecessary once open-telemetry/opentelemetry-js#5306 is released.

   You can try something similar to the following in your worker def and let me know if it works.

   import { HumanloopClient } from "humanloop";
   type Env = {
   	HUMANLOOP_API_KEY: string;
   }
   
   export default {
   	async fetch(request, env, ctx): Promise<Response> {
   		// Hack to fix @opentelemetry/sdk-trace-node
   		// Create a mock process object if it doesn't exist
   		const globalProcess = (globalThis as any).process || {};
   		// Set the version property if it doesn't exist
   		if (!globalProcess.version) {
   		  globalProcess.version = '16.0.0';
   		}
   		// Assign the mock process object to global scope
   		(globalThis as any).process = globalProcess;
   
   		const client = new HumanloopClient({ apiKey: env.HUMANLOOP_API_KEY });
   		return new Response(JSON.stringify(await client.directories.list()));
   	},
   } satisfies ExportedHandler<Env>;

   🚀React with 🚀1Reacted by Yor Jaggy
2. yorjaggy commented on Feb 24, 2025

   

   yorjaggy

   on Feb 24, 2025

   More actions

   I was having the same issue, thanks for that workaround @jamesbaskerville it works for me 🚀