Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Must use import to load ES Module: webpack.main.config.ts #3608

Open
3 tasks done
yusangeng opened this issue May 24, 2024 · 0 comments
Open
3 tasks done

Must use import to load ES Module: webpack.main.config.ts #3608

yusangeng opened this issue May 24, 2024 · 0 comments

Comments

@yusangeng
Copy link

Pre-flight checklist

  • I have read the contribution documentation for this project.
  • I agree to follow the code of conduct that this project uses.
  • I have searched the issue tracker for a bug that matches the one I want to file, without success.

Electron Forge version

7.4.0

Electron version

29.1.0

Operating system

WIndows 11(21H2)

Last known working Electron Forge version

Null

Expected behavior

The electron-forge make command successfully runs, packaging my project into an installer file.

Actual behavior

Error occured while running the electron-forge make command.

Must use import to load ES Module: mypath\webpack.main.config.ts
require() of ES modules is not supported.
require() of mypath\webpack.main.config.ts from
mypath\forge.config.cts is an ES module file as it is a .ts file whose nearest parent
package.json contains "type": "module" which defines all .ts files in that package scope as ES modules.
Instead change the requiring code to use import(), or remove "type": "module" from
mypath\package.json.

Note: My forge config file has been renamed to forge.config.cts, but it still be recognized as an ES module file.

Steps to reproduce

  1. Init an electron-foge project
  2. set "type" field to "module"(Because my project depends a package which use "exports" field to export entries, so I think I should set "type" to "module").
  3. npm run make

Additional information

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
1 participant