OpenAI module not found/failed to load module in Supabase edge functions

[j1philli]

Symptoms
Getting this log output when running my edge functions in Supabase
Failed to load module: "https://esm.sh/v133/openai@4.17.4/esnext/resources.js" - Import 'https://esm.sh/v133/openai@4.17.4/esnext/resources.js' failed, not found.

VS Code is throwing an error this when caching dependencies
Module not found "https://esm.sh/v133/openai@4.17.4/denonext/resources.js". at https://esm.sh/v133/openai@4.17.4/denonext/openai.mjs:7:13034

Looks like OpenAI isn't supporting esm.sh anymore for edge functions:
openai/openai-node#393 (comment)

Deno 1.38.1
Langchain .186

[dosubot]

🤖

Hi @j1philli, great to see you again!

I'm diving into the issue you've reported right now. Rest assured, I'll get back to you with a detailed response as soon as possible.

[dosubot]

🤖

Based on the issues you've described, it seems like you're encountering a problem with the OpenAI module not being found or failing to load in your Supabase edge functions. This issue has been encountered before in the langchainjs repository, and there are a few potential solutions you could try.

One solution that was suggested in a similar issue (ChatOpenAI breaks edge streaming on Vercel Edge functions.) was to bump the OpenAI dependency. This was resolved by a pull request: Bump OpenAI dep.

Another issue (OpenAI import fails in Vercel deployment Cannot find module '/var/task/node_modules/openai/_shims/agent-node.mjs') suggested downgrading to LangChainJS version 0.0.140 or upgrading to version 0.0.146. These versions use an older OpenAI SDK that doesn't cause the import error. The issue seems to be with the OpenAI SDK and not with LangChainJS itself.

Lastly, if you're having import problems with Deno on Supabase edge functions, you could try using esm with the following URL: https://esm.sh/langchain@0.0.122 as suggested in this issue: import problems with Deno on Supabase edge functions.

If OpenAI no longer supports ES modules for edge functions, you can use a CommonJS require statement instead of an ES6 import statement. Here's how you can modify your code:

const { ChatOpenAI } = require("langchain/chat_models/openai");
const { HumanMessage } = require("langchain/schema");
const { SerpAPI } = require("langchain/tools");

const model = new ChatOpenAI({
  temperature: 0.9,
  openAIApiKey: "YOUR-API-KEY", // In Node.js defaults to process.env.OPENAI_API_KEY
});

// You can also pass tools or functions to the model, learn more here
// https://platform.openai.com/docs/guides/gpt/function-calling

const modelForFunctionCalling = new ChatOpenAI({
  modelName: "gpt-4",
  temperature: 0,
});

await modelForFunctionCalling.predictMessages(
  [new HumanMessage("What is the weather in New York?")],
  { tools: [new SerpAPI()] }
  // Tools will be automatically formatted as functions in the OpenAI format
);

In this code, we're using the require function to load the ChatOpenAI, HumanMessage, and SerpAPI modules. This function is part of the CommonJS module system, which is supported by Node.js and thus by Supabase edge functions.

Unfortunately, I wasn't able to find the exact version of OpenAI SDK that langchainjs is currently using. You might want to check the package.json file in the langchainjs repository or the node_modules directory in your project for this information.

I hope this helps! If you have any other questions or need further clarification, feel free to ask.

Sources

• ChatOpenAI breaks edge streaming on Vercel Edge functions.
• OpenAI import fails in Vercel deployment Cannot find module '/var/task/node_modules/openai/_shims/agent-node.mjs'
• import problems with Deno on Supabase edge functions.
• examples/src/llms/openai.ts
• examples/src/models/chat/integration_openai.ts

---

This response is meant to be useful and save you time. It is not meant to be a precise solution, but rather a starting point for your own research.

Help me be more useful! Please leave a 👍 if this is helpful and 👎 if it is irrelevant.

If you want to continue the conversation, start your reply with @dosu-bot.

[jacoblee93]

For now, you can downgrade to 0.0.181, which should work - unfortunately not much we can do until the underlying SDK fixes it.

[j1philli]

@jacoblee93 the comment tagged in the issue sounds like they are not publishing to esm anymore

[jacoblee93]

Yeah :( hopefully they will start again soon.

[jacoblee93]

Hopefully fixed by the above ^