Forge-Build - no errors displayed when build failed

[elvince]

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.2.0

Electron version

28.2.2

Operating system

win 10

Last known working Electron Forge version

No response

Expected behavior

When there is a build issue, the terminal should provide the information of the error and stop processing other steps

Actual behavior

As of today:
✔ [plugin-webpack] Compiling main process code [23s]
✔ [plugin-webpack] Launching dev servers for renderer process code [2m9s]

Where as the main build is on error.
As a consequence, the launch process failed to find the main entry.

Steps to reproduce

Set a bad import in a TS file and launch the start process

Additional information

No response

[Harish-M-2003]

Hi! @elvince Could you please provide a minimal example of the TypeScript code where you introduced the faulty import statement? Including the TypeScript file(s) involved, along with any relevant configuration files or project setup details, will greatly assist in reproducing the issue on my system and investigating further.

[oohusl]

@Harish-M-2003 Any typescript error,
eg. app.whenReady2().then(()=>{})
app doesn't have method wenReady2

[Harish-M-2003]

@oohusl thanks for the reply, i'll look into it.

[erickzhao]

I can't seem to reproduce on my end with the typescript webpack template.

Errors are properly output when I yarn package:

ERROR in ./src/renderer.ts:33:13
TS2339: Property 'timeout' does not exist on type '{ new (): AbortSignal; prototype: AbortSignal; }'.
    31 | console.log('👋 This message is being logged by "renderer.js", included via webpack');
    32 |
  > 33 | AbortSignal.timeout(1000);
       |             ^^^^^^^
    34 |

webpack 5.97.1 compiled with 2 errors in 822 ms