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

Error at init AwesomeProject #225

Closed
imserhii opened this issue Mar 26, 2015 · 24 comments
Closed

Error at init AwesomeProject #225

imserhii opened this issue Mar 26, 2015 · 24 comments
Labels
Resolution: Locked This issue was locked by the bot.

Comments

@imserhii
Copy link

Hi there!
I have error at initialise your Awesome Project: screenshot 2015-03-26 20 27 13
Node v0.10.35, NPM 2.1.14

@ileonovdima
Copy link

@amasad
Copy link
Contributor

amasad commented Mar 26, 2015

can you paste npm-debug.log?

@ileonovdima
Copy link

@imserhii
Copy link
Author

Github don't like a too long comment :-) See in my Dropbox — https://www.dropbox.com/s/sts6bc2jr577kcm/npm-debug.log?dl=0

@ileonovdima
Copy link

@ileonovdima
Copy link

thank you

@amasad
Copy link
Contributor

amasad commented Mar 26, 2015

Did that work?

@imserhii
Copy link
Author

Yep! Thank you!
All who have same error write in terminal this:

sudo chown -R $USER ~/.npm
sudo chown -R $USER /usr/local/lib/node_modules

@Palgrover
Copy link

:)

@amasad
Copy link
Contributor

amasad commented Mar 26, 2015

Thanks @Palgrover!
Let's keep this open if more people run into this we need to handle it. It seems fragile that we rely on the postinstall script.

@mteece
Copy link

mteece commented Mar 26, 2015

Confirming that:

$ sudo chown -R $USER ~/.npm
$ sudo chown -R $USER /usr/local/lib/node_modules

Worked on my side.

@Palgrover
Copy link

Did anyone face the error

[Error: Watcher took too long to load
Try running watchman from your terminal
https://facebook.github.io/watchman/docs/troubleshooting.html]
Error: Watcher took too long to load
Try running watchman from your terminal
https://facebook.github.io/watchman/docs/troubleshooting.html
at null._onTimeout (/Users/WhackyApps/AwesomeProject/node_modules/react-native/packager/react-packager/src/FileWatcher/index.js:71:16)
at Timer.listOnTimeout (timers.js:110:15)

because of this i cannot reload my simulator after changes

@amasad
Copy link
Contributor

amasad commented Mar 26, 2015

@Palgrover can you open a new issue? we'll talk about it there

@Palgrover
Copy link

Sorry for that i have new issue guys lets discuss there

@Palgrover
Copy link

@amasad sure we can keep this open for sometime so that more people can solve it easily

@misuba
Copy link

misuba commented Mar 26, 2015

@amasad It Happened To Me. The chown fix worked great. I wonder if there is a commonality with people who have this issue maybe not having installed node with brew? (I didn't, I don't think.)

@mteece
Copy link

mteece commented Mar 26, 2015

I needed to chown the AwesomeProject folder after it was scaffolded by init.

@ClemMakesApps
Copy link

The extra $ sudo chown helped fix my issue as well

@robbestad
Copy link

Yeah, can confirm you will run into problems when you somtimes install dependencies as root (and thus end up with mixed ownership in the /usr/local/lib/node_modules folder and sometimes other /usr/local folders). It's the first thing I look at when people come to me with npm dependency problems.

@lucamezzalira
Copy link

it works for me too :D

@amasad amasad closed this as completed in a0e09fe Mar 27, 2015
amasad added a commit that referenced this issue Mar 27, 2015
Use only one package for dependencies, for now. Fixes #225
@amasad
Copy link
Contributor

amasad commented Mar 27, 2015

Can someone verify that this is fixed now?

vjeux pushed a commit to vjeux/react-native that referenced this issue Apr 13, 2015
Summary: some people are having issues with the postinstall script having to cd into the packager to npm install. This moves back all the packager deps to the root of the repo, this way there is no postinstall script. facebook#225

Test Plan:
* export oss
* npm install
* run ui explorer
@ghost
Copy link

ghost commented Apr 13, 2015

Nice , It `s fixed

$ sudo chown -R $USER ~/.npm


$ sudo chown -R $USER /usr/local/lib/node_modules

@san983
Copy link

san983 commented Aug 12, 2015

👍 worked for me

@facebook facebook locked as resolved and limited conversation to collaborators May 29, 2018
@react-native-bot react-native-bot added the Resolution: Locked This issue was locked by the bot. label Jul 23, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Resolution: Locked This issue was locked by the bot.
Projects
None yet
Development

No branches or pull requests