-
Notifications
You must be signed in to change notification settings - Fork 5
npx install failing - cannot spawn child process #57
Comments
I think the real solution is not use anything in cea-install.js that is not part of the standard NodeJS API. Will look into testing child-process again. |
CRA uses cross-spawn and it works fine from npx. I think it has to do with being a devdependency in CEA and CRA uses it as a regular dependency So the solution is to create separate dependencies for the package.json for the CEA vs the application it generates. This would obviously cause the unit tests to fail and would have to be rewritten to spawn a new application and test based on that. Which may actually be beneficial anyways. Or you can create and include it as a separate dev-utils package, which uses cross-spawn as just a regular dependency, which CRA also does with react-scripts. Also cross-spawn is a cross-platform replacement for child_process spawn which has issues on windows. It's probably a better idea to continue using it, unless you have any other suggestions. Or we could just not recommend npx at all. |
tested by ignoring that file, and now got this
😖 Not sure if |
Type of Change
Summary
Related to #54 , it looks like I had a local installation of create-evergreen-app, that was messing with things. I can now reproduce this across OSX, Linux, and Windows.
Details
Maybe we need npm install and npx? I was hoping npx would replace the need for a global install.
The text was updated successfully, but these errors were encountered: