That's not a "fix", that's a workaround - and not even a good one, since the bash (BTW, Windows 10 has a native one, you don't have to use the Git port for it...) breaks most people's workflows with their weird path formats.
So your actual problem remains unsolved which is sad.
Using the git bash works for me. So, my actual problem with incompatibilities alongside with the CMD or PowerShell command line is actually solved :).
Also, everything in %PATH% like the node.exe and stuff are available in the git bash.
Installing the native bash on Windows 10 is also a solution. But it involves installing Windows Subsystem for Linux and a Linux distribution (see: docs.microsoft.com/en-us/windows/w...).
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
That's not a "fix", that's a workaround - and not even a good one, since the
bash(BTW, Windows 10 has a native one, you don't have to use the Git port for it...) breaks most people's workflows with their weird path formats.So your actual problem remains unsolved which is sad.
(I suspect an incomplete
%PATH%...)Using the git bash works for me. So, my actual problem with incompatibilities alongside with the CMD or PowerShell command line is actually solved :).
Also, everything in
%PATH%like the node.exe and stuff are available in the git bash.Installing the native bash on Windows 10 is also a solution. But it involves installing Windows Subsystem for Linux and a Linux distribution (see: docs.microsoft.com/en-us/windows/w...).