ehmicky
ehmicky
Hi @alemagio, This repository is in standby mode at the moment. I unfortunately do not have time at the very moment to maintain it (except for quick dependencies upgrades) nor...
`awesome` `awesome-list` `node` `cross-platform` `portable` `portability` `compatibility` `windows` `macos` `macosx` `linux` `unix` `bsd` `os` `operating-system` `os-identification` `shell` `cmd` `environment-variables` `signal`
I don't have the permission to set topics.
@bcoe What do you think?
One big reason for the use of `cross-spawn` for me is being able to use shabangs on Windows.
Also `options.shell: true` fires the command through a shell instead of directly calling it. This is less secure, slower and less cross-platform: https://github.com/sindresorhus/execa/pull/182
I just tried `PATHEXT` with Node `11.13.0` on Windows 10 and `child_process.spawn()`. I can confirm it does not work unless `options.shell: true` is used.
List of cross-platform issues with `child_process.spawn()` (and related methods): 1) Shabangs are not supported on Windows. I.e. you need to do `spawn('node', ['./node_script.js'])` instead of `spawn('./node_script.js')` 2) on Unix, foreground...
For the 5 points I was mentioning: 1. I could see how some might object to making shebangs work on Windows. Windows uses file associations instead. And this is not...
Thanks for your answer! The similar error message happened yesterday: ``` Cannot create property 'message' on string 'Error in parsing SVG: Invalid attribute name Line: 1 Column: 57 Char: "'...