The problem with converting this module to CommonJS is this line:

If we compile this code to CommonJS this becomes a dynamic require, which the Wrangler bundler then complains about, since the esbuild output results in a dynamic `require("cloudflare:sockets") call.

Could we solve this instead by marking the package as an ESM module (i.e. "type": "module" in its package.json)?
Surely Vite(st) can handle packages that are declared ESM?

Surely Vite(st) can handle packages that are declared ESM?

Not in this case. These files don't get transformed by Vite, and are imported using the workerd module fallback service. This means they have strict module semantics, and require() can't be used to import an ES module. We should be able to keep the dynamic import() in the output rather than converting this to a require(). Not quite sure what the tsconfig.json incantation is though, will investigate more tomorrow. 👍

Looks like the magic incantation is "module": "Node16" and "moduleResolution": "Node16". This compiles to a CommonJS module, but keeps dynamic import()s in the output. 👍

Hey @petebacondarwin ! I'm also struggling with this issue - node-pg not working under Vitest.

Could we solve this instead by marking the package as an ESM module (i.e. "type": "module" in its package.json)? Surely Vite(st) can handle packages that are declared ESM?

I actually tried this, but then this line fails - https://github.com/brianc/node-postgres/blob/master/packages/pg/lib/stream.js#L41

const { CloudflareSocket } = require('pg-cloudflare')

As a proof of concept, I manually converted compiled node/modules/pg-cloudflare/dist/index.js to CommonJS syntax, and my test finally went through.

const { EventEmitter } = require('events'); // import { EventEmitter } from 'events';
class CloudflareSocket extends EventEmitter {
 // ...
}
module.exports.CloudflareSocket = CloudflareSocket;

Is there any research I should do to help push this through?

@unicoder88 - are you trying to get the library to work with Vitest in general or using the Cloudflare vitest-pool-workers integration?

@petebacondarwin , right, it's specifically Cloudflare vitest-pool-workers

We have a similar concern with the Vite Environments integration that we are working on.
Hopefully we can resolve this in a general way in the next few weeks.