-
Notifications
You must be signed in to change notification settings - Fork 875
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
dependencies not installed with 'npm install' #57
Comments
Those are all installed but not globally, did you check node_modules/.bin/ ? also try the scripts advertiesed in the readme i.e |
yeah, i ran:
And it failed because rimraf wasnt installed, so i did |
That's very odd, did the |
npm version 3.3.6, node version 0.12.2 npm install spat out a couple warnings about how js-beautify should be installed with -g and a couple other similar ones. And it also says that react-file-drop requires a peer of react, but none was installed. (also a warning). |
@whyrusleeping try doing |
wait, i need to go from node 0.12.2 to version 4.2.0 ? |
@whyrusleeping node 0.12.7, then iojs 1.x.x, 2.x.x, 3.x.x and then back to node in 4.0.0 and how will be node only onwards. Docs for all the versions https://nodejs.org/docs/ (plus vid for more context https://vimeo.com/138937671) |
While we are at it though, @whyrusleeping sheds light on an important detail: the scripts reference .bin paths explicitly! This is no good since npm hoists Lets get that fixed real quick. |
dude, i just cant javascript very well |
alright, install node 420 and ran npm install and npm start. same issue. |
deleted the repo, recloned, and got farther:
|
That sounds like a bug in https://github.com/ipfs/ipfs-geoip but I'm totally unclear as to why that only happens on your machine and not on mine. Stupid question, did you stop your ipfs daemon before? |
@bcomnes I'm sorry I'm not seeing how referencing |
npm adds |
Okay, so the issue with that is yes it works most of the times, but I had a lot of issues with this assumption especially with |
@whyrusleeping did you get any further? |
Just cloned the repo and can reproduce this with the same steps. Full output
|
@victorbjelkholm try updating your npm to version 3, as @dignifiedquire said:
|
updated and tried again and got the same error as @victorbjelkholm |
removed my
|
Hm, reinstalled npm to version 3.3.8 (although I don't understand why 2.X wouldn't work?) and starts ok but doesn't run. Seems like
|
station doesn't stay on for long, crashing for me:
|
@diasdavid :(
|
I was able to reproduce, it seems it only happens when initializing a new node and then connecting |
This is the error I got https://gist.github.com/Dignifiedquire/dd288f9332e11ac797a6 as far as I can tell the underlying issue is a
|
Fresh install, getting unresolved peer dependency issues with npm3.
|
@bcomnes i get that every time too, but i ignored it since it was a warning. |
Same here:
with electron, rimraf and babel globally installed. Worked also with soley electron-prebuit installed, too.
maybe also worth a new issue? Querying for |
Please try again with latest |
Confirmed for Node 5.3.0 + npm latest + clean cache. always rm -rf'ed the node_modules On 20 December 2015 at 10:24, Friedel Ziegelmayer notifications@github.com
|
@almereyda what do you mean with "confirmed for node 5.3.0", that the same issue exists or that it works? |
Just closed the tabs for the node 4 one: some |
I think we should close this because this doesn't happen anymore. /cc @diasdavid |
Woot! thank you @hacdias !! :) |
I cloned the repo down and followed the setup instructions and still needed a few things:
rimraf
babel
There may be more, but I'm stuck on the electron issue.
The text was updated successfully, but these errors were encountered: