For namespaces, the generated bundle type definitions doesn't declare exactly what the generated module exposes about ohm

[pdubroy]

Here, the module is an object with two properties, Foo and Bar. Said differently, the JavaScript module consists of two named properties.

Hmmm, I'm not sure I'd put it that way. The module has a single export, which is a Namespace object. That object has two properties.

The way it's declared was based on the recommendation from the TypeScript documentation on .d.ts files. I didn't realize that it requires the use of esModuleInterop, but I see from the documentation that you're right about that.

I could see a few possible ways forward:

• The documentation mentions using the old export = syntax. Would it be preferable for us to use that instead?
• Maybe there is little value in Namespace objects, and it would be simpler to just use regular, named exports.