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

create-react-app fails to create a project on windows 10 #1587

Closed
dcu-sharepoint opened this issue Feb 18, 2017 · 30 comments
Closed

create-react-app fails to create a project on windows 10 #1587

dcu-sharepoint opened this issue Feb 18, 2017 · 30 comments

Comments

@dcu-sharepoint
Copy link

dcu-sharepoint commented Feb 18, 2017

Can you reproduce the problem with latest npm?

yes; using npm 4.1.2

when executing the command:

create-react-app

the terminal window disappears (ie: exits) and NOTHING GETS CREATED!

tried with and w/o sudo privs with same terminal window results

this happens with create-react-versions 1.0.3 and 1.0.4

have tried to reproduce the issue again and again and again and again and .......

Can you still reproduce it?

yes

Expected behavior

have create-react-app CREATE AN APP!.

Actual behavior

when executing the command:

create-react-app

the terminal window disappears (ie: exits) and NOTHING IS CREATED

tried with and w/o sudo privs with same terminal window results

this happens with create-react-versions 1.0.3 and 1.0.4

have tried to reproduce the issue again and again and again and again and .......

Environment

Run these commands in the project folder and fill in their results:

  1. node -v: v6.9.5
  2. npm -v: v4.1.2
  3. Operating system: Microsoft Windows 10 Enterprise 10.0.14393 Build 14393
  4. Browser: Chrome v56.0.2924.87 (64-bit)
@gaearon
Copy link
Contributor

gaearon commented Feb 18, 2017

Can you show a screenshot of how you run it? Are you using Cmd or PowerShell?

@dcu-sharepoint
Copy link
Author

dcu-sharepoint commented Feb 18, 2017 via email

@dcu-sharepoint
Copy link
Author

dcu-sharepoint commented Feb 20, 2017 via email

@gaearon
Copy link
Contributor

gaearon commented Feb 20, 2017

I don't see a PowerShell screenshot, can you attach it please?

Please keep in mind this is an open source project. We try to help you but since this issue doesn't occur for a vast majority of users, we will need more help and information to diagnose it.

@dcu-sharepoint
Copy link
Author

dcu-sharepoint commented Feb 21, 2017 via email

@gaearon
Copy link
Contributor

gaearon commented Feb 21, 2017

I think you'll need to use GH web interface. If you're attaching a file via email, it gets ignored.

@dcu-sharepoint
Copy link
Author

dcu-sharepoint commented Feb 21, 2017 via email

@dcu-sharepoint
Copy link
Author

dcu-sharepoint commented Feb 21, 2017 via email

@tbillington
Copy link

tbillington commented Feb 21, 2017

@dcu-sharepoint GH = GitHub. You can drag images onto the text entry box on this issue on github.com and it will upload the image to GitHub and include it in your message. It's not possible to send images from email (as far as I know).

@dcu-sharepoint
Copy link
Author

dcu-sharepoint commented Feb 21, 2017 via email

@dcu-sharepoint
Copy link
Author

dcu-sharepoint commented Feb 21, 2017 via email

@gaearon
Copy link
Contributor

gaearon commented Feb 21, 2017

Let's continue the discussion in this topic. #1594 is an unrelated thread.

What I'm seeing from your screenshot in #1594 (comment) is that Yarn command doesn't seem to work correctly.

I think this might be a Yarn bug: yarnpkg/yarn#2192. You can try the workarounds described in it, but I'd suggest just uninstalling Yarn for the time being. Create React App will fall back to npm if Yarn isn't installed, and that should solve your issue.

Hope it helps!

@dcu-sharepoint
Copy link
Author

dcu-sharepoint commented Feb 21, 2017 via email

@gaearon
Copy link
Contributor

gaearon commented Feb 21, 2017

I tried both NPM and YARN and both give me the same error or behaviour

To be clear, Create React App always uses Yarn if it is installed. So I recommend trying to uninstall it, and then Create React App will fall back to npm. If this solves the problem, then it was a Yarn bug.

@dcu-sharepoint
Copy link
Author

dcu-sharepoint commented Feb 21, 2017 via email

@gaearon
Copy link
Contributor

gaearon commented Feb 21, 2017

Maybe you still have a broken create-react-app installation from Yarn.

Try running

npm install -g create-react-app

Then try running create-react-app again.
If it doesn't work, please post another screenshot so we can continue looking into this.

@dcu-sharepoint
Copy link
Author

@gaearon Yarn is caputed! create-react-app has been caputed!, system has been rebooted, any folders mentioning yarn have been caputed!. using the windows control panel->programs->uninstall yarn has been executed to remove yarn completely of the system, and the only thing I can think of is if "create-react-app" or yarn puts anything on the registry but I work with a non-administrator account and I did not find anything on the windows registry with yarn in it.

still buffled... 👎 :(

@gaearon
Copy link
Contributor

gaearon commented Feb 21, 2017

Have you tried what I suggested above?

npm install -g create-react-app

I think you need to do that to redirect the global command to the new location.

@dcu-sharepoint
Copy link
Author

dcu-sharepoint commented Feb 21, 2017

@gaearon 1: I've removed, re-installed, re-removed, re-re-installed, re-re-removed, re-re-re-failed again...

2: if I move the globals folder then I REALLY will get all screwed up because I have a complete application infrastructure that is working well with REACT and bunch of other Microsoft modules for me and it took me a L O O O N G time to setup, so that is not an option.

However, you just gave me an idea that I'm going to try later on in the afternoon and that is to open a new user account and dedicate it to react/create-react-app playground and see if that works, because it will have a virgin globals folder and no yarn corrupting influence. Stay tuned... more to come...

@gaearon
Copy link
Contributor

gaearon commented Feb 21, 2017

Sounds good. Sorry for the trouble. Yarn is generally working pretty well but there are annoying bugs like this on some systems.

@dcu-sharepoint
Copy link
Author

yeah, Yarn is also giving me problems with an MS app in widows where it is looking for an apple mac environmental issue in a WINDOWS environment and the app install fails. I posted the issue in the yarn site about a month ago.

@dcu-sharepoint
Copy link
Author

dcu-sharepoint commented Feb 21, 2017

anywho: will keep u posted, Gracias....

@gaearon
Copy link
Contributor

gaearon commented Feb 24, 2017

Going to close this because all the problems appear related to the installation of create-react-app itself which is managed by either Yarn or npm. There’s nothing we can do there.

@gaearon gaearon closed this as completed Feb 24, 2017
@jmanzo
Copy link

jmanzo commented Aug 9, 2017

I think that you should start using a Node Console for decompose the issue. Did you had success? I had a problem similar and I solved it using the Node Console. Regards!

@pawelpodkowa
Copy link

yes node console and -g global settings resolved problem for sure :)

@cziem
Copy link

cziem commented Nov 22, 2017

@gaearon I have done npm install -g create-react-app and yet I get error messages
createreactapp

@tanwill
Copy link

tanwill commented Dec 11, 2017

phavor, try running from administrator. Right click the command prompt in the search bar, run as admin, then install create-react-app again. This is the equivalent to running sudo on Linux.

@ali0053
Copy link

ali0053 commented Feb 23, 2018

issue
can anyone help me with this issue??

@themre
Copy link
Contributor

themre commented Feb 23, 2018

@ali0053 have you tried closing CMD and opening it again?

@dextel2
Copy link

dextel2 commented Oct 15, 2018

@ali0053 npx create-react-app should help you

@facebook facebook locked as resolved and limited conversation to collaborators Oct 15, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

10 participants