npm run start not working, no logs on windows.

[zenovak]

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.

Forge version

7.6.1

Electron version

34.0.0

Operating system

Windows 11 Version 10.0.26100 Build 26100

Last known working Forge version

No response

Expected behavior

run the development as usual

Actual behavior

The run start command completely shuts down for no aparrent reasons. This was the only logs that was available from npm verbose.

 verbose cli C:\Program Files\nodejs\node.exe C:\Users\Zenovak\AppData\Roaming\npm\node_modules\npm\bin\npm-cli.js
1 info using [email protected]
2 info using [email protected]
3 silly config load:file:C:\Users\Zenovak\AppData\Roaming\npm\node_modules\npm\npmrc
4 silly config load:file:D:\Projects\electron\folder-archive\.npmrc
5 silly config load:file:C:\Users\Zenovak\.npmrc
6 silly config load:file:C:\Users\Zenovak\AppData\Roaming\npm\etc\npmrc
7 verbose title npm run start
8 verbose argv "run" "start"
9 verbose logfile logs-max:10 dir:C:\Users\Zenovak\AppData\Local\npm-cache\_logs\2025-03-11T16_35_08_130Z-
10 verbose logfile C:\Users\Zenovak\AppData\Local\npm-cache\_logs\2025-03-11T16_35_08_130Z-debug-0.log
11 silly logfile start cleaning logs, removing 4 files
12 silly logfile done cleaning log files
13 verbose cwd D:\Projects\electron\folder-archive
14 verbose os Windows_NT 10.0.26100
15 verbose node v18.18.1
16 verbose npm  v10.8.3
17 verbose exit 1
18 verbose code 1

Additional information when running npm run start shows program exited

The same problem also occured in newly bootstrapped app. Is there something that was misconfigured on my machine somewhere? I couldnt find any information on this

Steps to reproduce

No idea.

Additional information

No response

[erickzhao]

Hi @zenovak, this could be related to #3875, where Forge no longer outputs start errors correctly.

I've been investigating the root cause of that regression but don't have a solution yet. Could you try rerunning with the DEBUG=electron-forge:* flag or alternatively downgrade to v7.5.0 for testing purposes?

[zenovak]

Thanks for the speedy response. It seemed like a temporary hiccup on my machine. Has worked correctly after a restart.