[bug] No "exports" main defined in /path/to/node_modules/@arizeai/openinference-genai/package.json

[syl67]

Describe the bug

The @arizeai/openinference-genai package fails to load when imported through @mastra/arize in a CommonJS environment. Node.js throws an error: "No 'exports' main defined" because the package only defines ESM (import) exports in its package.json, but no CommonJS (require) exports.

To Reproduce

1. Install @mastra/arize (version ^0.1.1) which depends on @arizeai/openinference-genai
2. Import ArizeExporter from @mastra/arize in a TypeScript file
3. Run the application using ts-node-dev (which compiles to CommonJS by default)
4. The application will crash with the following error:

Error: No "exports" main defined in /path/to/node_modules/@arizeai/openinference-genai/package.json
    at exportsNotFound (node:internal/modules/esm/resolve:314:10)
    at packageExportsResolve (node:internal/modules/esm/resolve:604:13)
    at resolveExports (node:internal/modules/cjs/loader:657:36)
    at Function._findPath (node:internal/modules/cjs/loader:749:31)
    at Function._resolveFilename (node:internal/modules/cjs/loader:1387:27)
    ...

Expected behavior

The @arizeai/openinference-genai package should provide both ESM and CommonJS exports in its package.json to support both module systems, or at minimum provide a fallback main field for CommonJS compatibility.

Screenshots

N/A

Desktop (please complete the following information):

• OS: macOS (darwin 24.6.0)
• Node.js Version: 22.x
• Package Version: @arizeai/openinference-genai@0.1.0

Additional context

The @arizeai/openinference-genai package.json currently has:

• "type": "module" (ESM-only)
• exports field with only "import" conditions, no "require" conditions
• No main field for CommonJS fallback

This causes issues when:

• The consuming application uses CommonJS (via ts-node-dev or compiled TypeScript)
• The package is imported transitively through @mastra/arize

[dosubot]

The error happens because @arizeai/openinference-genai only provides ESM exports—there are no CommonJS (require) exports or a main field in its package.json, so Node.js can't load it in a CommonJS environment. This is a known issue and has been confirmed by both users and maintainers; similar problems have been fixed in other OpenInference packages, but no merged fix exists yet for this one.

A workaround that sometimes helps is to set "module": "nodenext" in your tsconfig.json if you're using TypeScript, which can let Node.js and TypeScript resolve mixed ESM/CommonJS exports more gracefully. If that's not an option, you may need to use an ESM-only workflow or a bundler that can handle ESM dependencies in CommonJS projects.

There's no official ETA for a fix, but maintainers are aware and have indicated it should be straightforward to resolve. You can follow the ongoing discussion and see recent maintainer responses in this thread.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}

   

[techno-anthropology]

cc @cephalization, @syl67 brought up in #2501

[cephalization]

Thanks for the details, this is exactly the details I needed. The openinference gen ai package was shipped as ESM only to evaluate if commonjs use cases were still relevant, as shipping both module types adds maintenance burden.

I don't think it breaks too many assumptions on our part to also ship commonjs for this module.

Let me evaluate the impact and get back to you

[cephalization]

I need to do validation but I am exploring the impact of commonjs builds here #2505

If you want, you can test overriding the openinference-genai package in your package.json with this development build https://pkg.pr.new/Arize-ai/openinference/@arizeai/openinference-genai@2505 and replace the version of openinference-genai within mastra/arize with this

@syl67 let me know if you can validate this