'electron-forge' is not recognized as an internal or external command (Windows 10)

[gnesher]

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.47
• Electron Version:
  v7.1.10
• Operating System:
  Windows 10 Pro, 1909
• Last Known Working Electron Forge version::
  N/A

Expected Behavior

Followed installation guide using npx, and tried to run 'npm start' expected the application to start, instead, I'm getting the following error: 'electron-forge' is not recognized as an internal or external command,

Actual Behavior

The application fails to start, throwing an error - 'electron-forge' is not recognized as an internal or external command,

To Reproduce

Follow npx install procedure on a windows machine

Additional Information

There's a closed ticket from 2018 regarding a similar error that happened when directory included spaces. I believe it was solved, regardless my folder does not contain spaces (test-ble-electron)

[malept]

Can you reproduce this on a different machine?

What version of npx are you running?

[gnesher]

$ npx -v
6.13.4

I'll try reproducing it on another machine later today, I don't have another development setup here

[malept]

I can't reproduce this on a clean Windows 10 installation where I just installed the latest version of Node.js 12 and git.

[malept]

I stand corrected - I can reproduce this, but only under weird circumstances. I ran npx create-electron-app test under WSL and then tried running npm start in Powershell/CMD. This will not work because WSL is Linux and not Windows. The solution is to delete the node_modules folder and re-run npm install.

[gnesher]

@malept That makes sense, however, I'm using Git Bash :/

[malept]

I can't reproduce this with just using Git Bash, either.

[Tapestes]

Had the same problem. Best as I can tell it was a Path issue. Uninstalling node and reinstalling fixed it for me.