Typing rs in the terminal does not restart the dev environment app

[b-zurg]

Preflight Checklist

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

Issue Details

• Electron Forge Version:
  6.0.0-beta.57
• Electron Version:
  v11.3.0
• Operating System:
  Macos big sur latest

Expected Behavior

I expect to be able to run electron forge and type in the terminal rs and have the entire app restart.

Actual Behavior

The app does not restart when I type in rs

Additional Information

I think this could be related to the recent changes in the webpack plugin upgrade to webpack version 5

[ltabis]

Hey @b-zurg, I've encountered this issue in a project, and couldn't find any solution to fix this problem. I think it's definitely a webpack 5 bug since I've just updated to that version and that's when the problem occured.

I've nonetheless managed to re-enable the rs command by passing the env variable DEBUG='electron-forge:*' to the start script (I was trying to see what electron-forge was doing under the hood to find the problem) in my package.json like so:

 "scripts": {
    "start": "cross-env DEBUG='electron-forge:*' NODE_ENV=development electron-forge start --inspect-electron",
  },

(cross-env is used to enable windows devs to use the same config as linux users)

I know it's not a good solution and that it might not work for you, but please give it a try while this is being worked on.
(btw I have no idea why enabling logs would re-enable the rs command :/)

[rumtraubenuss]

rs + enter in terminal does also not work in 6.0.0-beta.61.

@ltabis setting the DEBUG env as you mentioned re-enables the rs command for me. 👍💯
For a quick test without altering package.json prefixing the npm start command like this worked for me (on mac os):
DEBUG='electron-forge:*' npm start

[tr3ysmith]

So maybe this is related, but on my Mac, I'm seeing this same issue not only with Electron Forge but also with nodemon... maybe related?

[wobedi]

An even more minimal workaround (which still works for me) is to scope the DEBUG variable to just the webpack plugin:

DEBUG='electron-forge:plugin:webpack' npm start

[clavin]

After a very deep dive, I've figured out that this is caused by ora (which we use for those little command-line spinners) which internally uses node:readline. When ora completes, it closes the readline session which, in turn, pauses the input stream, due to an undocumented quirk in node:readline. This means that stdin is paused and thus we never receive the data.

Filed an upstream bug and PR for this: sindresorhus/ora#209