PATH variable replacement on Windows envirement about cross-env HOT 3 CLOSED

Yes, this is an interesting problem. I think it's a worthwhile feature, so I'd be happy to accept a pull request for this. Would you be willing to implement that? I'm not sure we need to use path-key because the code will literally just be: const pathKey = isWindows ? 'Path' : 'PATH' (thanks to https://github.com/kentcdodds/cross-env/blob/master/src/is-windows.js).

Would you be interested in implementing this?

from cross-env.

The problem was deeper...

On Windows operating systems, environment variables are case-insensitive.
However, if when you spawn a new process and pass the env with two variables (PATH and Path), in this new process process.env will contains both variables, and this breaks the subsequent logic.

Npm has logic to set both Path and PATH (if exist) variables on Windows, and by default used Path on Windows.
But if I use cgwin terminal on Windows for example, process.env contains PATH.

from cross-env.

#257

from cross-env.