Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

npx create-react-app spawn ENOENT? #16099

Closed
Eric-Johnston opened this issue Jul 10, 2019 · 1 comment
Closed

npx create-react-app spawn ENOENT? #16099

Eric-Johnston opened this issue Jul 10, 2019 · 1 comment

Comments

@Eric-Johnston
Copy link

Eric-Johnston commented Jul 10, 2019

Do you want to request a feature or report a bug?
Bug

What is the current behavior?
Using npx create-react-app causes a "spawn enoent" error that points to my mongoDB folder. This only began after I installed mongoDB.

$ npx create-react-app client
spawn C:\Program Files\MongoDB\Server\4.0\bin ENOENT

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem. Your bug will get fixed much faster if we can run your code and it doesn't have dependencies other than React. Paste the link to your JSFiddle (https://jsfiddle.net/Luktwrdm/) or CodeSandbox (https://codesandbox.io/s/new) example below:
The steps I took to experience this bug was to install mongoDB and attempt to create a react app. Somehow I doubt following those steps will recreate the bug, however.

What is the expected behavior?
The expected behavior is that I'm able to create a new react app without any errors.

Which versions of React, and which browser / OS are affected by this issue? Did this work in previous versions of React?
Version 16.8.6.

@CherryDT
Copy link

CherryDT commented Oct 11, 2021

Same as facebook/create-react-app#7347

Seems this keeps popping up though, see also here and here and here (the latter having a slight variation, failing on the MongoDB data path instead of bin)

EDIT:

Seems the culprit is a messed-up COMSPEC variable. For some reason it is actually set to the path shown here...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants