Windows support on the bash/sh code
See original GitHub issue`events.js:182 throw er; // Unhandled ‘error’ event ^
Error: spawn bash ENOENT `
Issue Analytics
- State:
- Created 5 years ago
- Comments:15 (9 by maintainers)
Top Results From Across the Web
How To Use Bash Shell Natively On Windows 10
How To Use Bash Shell Natively On Windows 10 · Start -> Settings -> Update&Security. · Selecting the developer mode will pop the...
Read more >How to run .sh or Shell Script file in Windows 11/10
1] Execute Shell Script file using WSL · Open Command Prompt and navigate to the folder where the script file is available. ·...
Read more >How to Create and Run Bash Shell Scripts on Windows 10
With the arrival of Windows 10's Bash shell, you can now create and run Bash ... Bash commands into a Windows batch file...
Read more >How do I use Bash on Windows from the Visual Studio Code ...
Install Git from https://git-scm.com/download/win. Open Visual Studio Code and press and hold Ctrl + ` to open the terminal.
Read more >Discover the power of Bash on Windows - InfoWorld
Bash on Windows is a new feature added to Windows 10. Microsoft has teamed up with Canonical, aka the creators of Ubuntu Linux,...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@olstenlarck just to be clear, I was inputting that only cross-spawn could be considered versus using exca. Use whatever you want though and the exca project is certainly more than cross-spawn.
I’m not understanding the “waste time” comment; However, for me it was not a waist of time and I hope this helps the project and someone else like it helped me.
@olstenlarck
Here you go
Pretty much the simplest task will fail. It seems like there is a lack of Windows machines used to test on. I think the error clearly shows “sh” or “bash” does not exist to execute or spawn.