Consider dual publishing commonjs

[Stono]

Description

Hi,
So you've recently made this module ESM only.

Whilst I support the general move towards ESM; realistically moving our entire estate to support ESM is a mammoth task. The way that unfortunately manifests for me is that I'll either need to fork this module and make it non-esm, or find an alternative (or write my own), because I don't see us managing to migrate an entire legacy estate to support esm any time soon.

Appreciate you may not want to do this, if so please just close the issue and i'll have my answer and know which direction I need to take :)

OpenAPI specification (optional)

No response

Configuration

No response

System information (optional)

No response

[mrlubos]

Nope, I think we will want this @Stono 🤝 interestingly, you're the only one who complained so far, I was expecting more reports sooner

[jordanshatford]

@Stono Would you be able to help out with this. Or provide a repository for reproduction. Unfortunately I do not think my initial fix will solve this

[jordanshatford]

Have pushed changes which I was able to test and appear to fix this issue. Was able to properly generate with both CJS and ESM, when before my changes it would fail with CJS

[mrlubos]

@Stono This should be now fixed, can you give it a try? Awesome work @jordanshatford 🎉