You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Node.js spawn results in ENOENT on Termux/Android, despite the command (in my case, npm) being installed, and in the PATH found in process.env. The Termux devs claim this works correctly on Android 10, but they dropped Android 5.0 support last year or two ago and will not update Node binary.
On the Node.js repo, in an older bug related to Windows, bnoodhuis has stated that such issues will never be "fixed", as the recommended "solution" is to use the { shell: true } option or use exec. Tested with the shell set to true and the npm command was properly executed.
This bug effects create-react-app on my Android 5.0 device running Termux with Linux 3.4.0, node 12.13.0 and npm 6.14.8. create-react-app is using cross-spawn 7.0.3 (current at time of writing).
It seems like cross-spawn would be an ideal place to land a fix. However, I have also contacted create-react-app. But as that project is so large and with so many untriaged open issues, my hopes are not high for a resolution there.
Any further advice welcomed. Please assume that this device and OS and platform is a given constraint and valid without needing to justify myself or be pressured to conform. Were situation different, this would not be my first choice, but such is life. My concern is simply platform support or reasonable workaround.
The text was updated successfully, but these errors were encountered:
Node.js spawn results in ENOENT on Termux/Android, despite the command (in my case, npm) being installed, and in the PATH found in process.env. The Termux devs claim this works correctly on Android 10, but they dropped Android 5.0 support last year or two ago and will not update Node binary.
On the Node.js repo, in an older bug related to Windows, bnoodhuis has stated that such issues will never be "fixed", as the recommended "solution" is to use the { shell: true } option or use exec. Tested with the shell set to true and the npm command was properly executed.
This bug effects create-react-app on my Android 5.0 device running Termux with Linux 3.4.0, node 12.13.0 and npm 6.14.8. create-react-app is using cross-spawn 7.0.3 (current at time of writing).
It seems like cross-spawn would be an ideal place to land a fix. However, I have also contacted create-react-app. But as that project is so large and with so many untriaged open issues, my hopes are not high for a resolution there.
Any further advice welcomed. Please assume that this device and OS and platform is a given constraint and valid without needing to justify myself or be pressured to conform. Were situation different, this would not be my first choice, but such is life. My concern is simply platform support or reasonable workaround.
The text was updated successfully, but these errors were encountered: