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 errors: spawn ENOENT #7347

Closed
Eric-Johnston opened this issue Jul 10, 2019 · 2 comments
Closed

npx create-react-app errors: spawn ENOENT #7347

Eric-Johnston opened this issue Jul 10, 2019 · 2 comments

Comments

@Eric-Johnston
Copy link

Eric-Johnston commented Jul 10, 2019

Describe the bug

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

Did you try recovering your dependencies?

Not relevant, I can't even start a project.

Which terms did you search for in User Guide?

spawn, ENOENT, mongodb

Environment

Using Windows 10, node version 10.16.0.

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

Seems I receive the same error using this command as well.

Steps to reproduce

(Write your steps here:)

  1. Install mongoDB
  2. run command 'npx create-react-app client'
  3. receive this error:
    $ npx create-react-app client
    spawn C:\Program Files\MongoDB\Server\4.0\bin ENOENT

Expected behavior

I should be able to create a react app without issue.

Actual behavior

I'm receiving this error:

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

Reproducible demo

I have no idea how to reproduce this on another machine. I was able to install mongoDB on a separate computer and I don't have this issue. I assume the vast majority of people are able to install mongoDB on their machine without experiencing this issue.

@heyimalex
Copy link
Contributor

I have no idea why create-react-app would be trying to call C:\Program Files\MongoDB\Server\4.0\bin, so something is really messed up somewhere. Maybe npm cache clean --force?

@fritzschoff
Copy link

close ?

@lock lock bot locked and limited conversation to collaborators Oct 23, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants