feat: esm forge.config.js support

[mahnunchik]

• I have read the contribution documentation for this project.
• I agree to follow the code of conduct that this project follows, as appropriate.
• The changes are appropriately documented (if applicable).
• The changes have sufficient test coverage (if applicable).
• The testsuite passes successfully on my local machine (if applicable).

Summarize your changes:

This tiny PR adds ESM config support. Test added. Closes #3350

It is not a breaking change. Be ready for Electron 28 with ESM support! 💯

[mahnunchik]

Of course, I understand that it is better to (1) update typescript (2) update target to esnext, (3) update module resolution to esnext too (4) replace interpret and rechoir with something working with esm but this small fix allow to use ESM config without such big changes 😉

[mahnunchik]

I think the failing Windows tests are not related to the changes.

[mahnunchik]

Related #3129

[MarshallOfSound]

We cant ship code that depends on string templated eval, that's neither safe nor generally good practice

[mahnunchik]

@MarshallOfSound maybe you know how to make quite old typescript to not compile dynamic import?

Or if you plan to upgrade typescript and compiled module type it should be pretty easy.

[MarshallOfSound]

Make a plain JS file that exports a helper that uses the dynamic import method. Not pretty but better than eval imo

[mahnunchik]

@MarshallOfSound if dynamic import is in js file it is compiled to require.... I need help to figure it out.

return Promise.resolve().then(() => __importStar(require(path)));

[mahnunchik]

@MarshallOfSound I think I was able to get it to work with the current version of ts. Could you please check the current implementation?

[mahnunchik]

Windows tests are fixed!

[mahnunchik]

@MarshallOfSound @erikian @erickzhao what can I do to ship this feature?

[mahnunchik]

@MarshallOfSound @erikian @erickzhao it is me again 😉 What should I do to ship this feature?

[himself65]

hi, what's the update on this progress?

[Jayatubi]

Looks like it doesn't work with forge.config.ts.

The dynamicImport would fail with ts version config path and esm on:

code:
'ERR_UNKNOWN_FILE_EXTENSION'
message:
'Unknown file extension ".ts" for E:\project\forge.config.ts'