🧪 TypeError: API.Completions is not a constructor

[NatoBoram]

This reproduces the error API.Completions is not a constructor in a minimal project that mimics some real-world requirements, such as loading environment variables and starting an Express server.

Before this pull request

• OpenAI is installed
• Sentry is installed and preloaded
• The pipeline confirms that the project is working as expected

In this pull request

• OpenAI is called with new OpenAI()
• A test is added to make sure that it is possible to call new OpenAI()
• The pipeline fails at running dist/index.js
• The unit test index.test.ts fails or timeouts

❯ node --import @sentry/node/preload ./dist/index.js
TypeError: API.Completions is not a constructor
    at new OpenAI (file:///home/nato/Code/github.com/NatoBoram/bug-report-sentry/node_modules/.pnpm/openai@4.51.0/node_modules/openai/index.mjs:46:28)
    at file:///home/nato/Code/github.com/NatoBoram/bug-report-sentry/dist/openai.js:3:23
    at ModuleJob.run (node:internal/modules/esm/module_job:262:25)
    at async ModuleLoader.import (node:internal/modules/esm/loader:474:24)
    at async asyncRunEntryPointWithESMLoader (node:internal/modules/run_main:109:5)
(node:368685) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
(Use `node --trace-deprecation ...` to show where the warning was created)

• SDK fails in ESM mode in combination with openai getsentry/sentry-javascript#12414
• TypeError: API.Completions is not a constructor openai/openai-node#897

[NatoBoram]

Confirmed fixed in Sentry v8.13.0