Taking the Ecosystem Forward: An Update on the Future of Connect

We submitted our feedback using the link in the blog post, but we just discovered another potential blocker (relating to Forge resolver functions seemingly not working when type: "module" is specified in the main package.json file - see footnote below).

To @scott.dudley 's point about a private survey being a particularly bad way to gather this sort of feedback, what should we do if we wish to amend/append more feedback to our earlier submission? Submit another survey response?

Footnote:

We’re aware of the closed issue FRGE-1298, but this seems to still be a problem.
When type: "module" is specified, our resolver function errors with

There was an error invoking the function - forge_resolver__WEBPACK_IMPORTED_MODULE_0_ is not a constructor

When the type is removed (which defaults the project to CJS), the error no longer occurs.

Come on guys, it’s 2025. ESM is no longer new/experimental. Forge should not break in the face of ESM-based projects.

10 Likes