-
Notifications
You must be signed in to change notification settings - Fork 323
'npm run local' throws error after fresh clone and following guide #70
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
Comments
Turns out I had to update NPM and Node to latest. Perhaps consider requiring specific versions of these, and adding this to the FAQ, or mentioning it somewhere :) |
@pathurs Sorry about that! I did mention on the readme that "latest LTS
version" of node is recommended, but I'll admit it's a little vague.
I'll change it when I'm out of work to be more clearer. Technically you
should be fine with anything above Node v6.0.0.
…On Wed, 13 Sep 2017, 19:12 Pathurs ***@***.***> wrote:
Turns out I had to update NPM and Node to latest.
Perhaps consider requiring specific versions of these, and adding this to
the FAQ, or mentioning it somewhere :)
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#70 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AFZshZUq2WCBESSeXn1486Bjmv73Vwukks5sh8bIgaJpZM4PV_z9>
.
|
Wasn't a huge problem, however knowing that this is intended for "noobs", then I figured someone in my situation without my knowledge could have been 10x more confused |
Think I am still having similar error but attaching my log file. I Just updated node which node is at 8.7.0 and npm is at 5.4.2. The only other strange thing when I do npm install it says typings is depcrated not sure if that is a problem. Any help would be appreciated. |
@wolffman122 What did the console say before throwing out the error? If it's the same as above, try installing Also, |
@resir014 also do you have any instructions on installing those two things I am not to familiar how to? |
@wolffman122 Hmm. It seems your credentials.json file might be broken. Try
deleting the keys that are blank and try again.
…On Tue, 24 Oct 2017, 07:52 wolffman122, ***@***.***> wrote:
[image: image]
<https://user-images.githubusercontent.com/19178872/31919995-0d09d0d4-b834-11e7-8725-950a95d184cf.png>
[image: image]
<https://user-images.githubusercontent.com/19178872/31920000-1d0df154-b834-11e7-83cd-c5d21e7bfbee.png>
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#70 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AFZshYuWNy7j3txg3F4Q_mHWGCytZHFHks5svTTegaJpZM4PV_z9>
.
|
@resir014 i have my credentials.json open and put my emailin, then password, do i have to put anything in for TOKEN or SERVER_PASS if i am doing this on the production screeps server? Not sure where the keys you are referring to are |
Ah yeah, TOKEN and SERVER_PASS are meant for private servers only, so
remove those keys.
This was undocumented and the common source of issues. I'll try to document
later when I've arrived at my workplace.
…On Tue, 24 Oct 2017, 07:59 wolffman122, ***@***.***> wrote:
@resir014 <https://github.com/resir014> i have my credentials.json open
and put my emailin, then password, do i have to put anything in for TOKEN
or SERVER_PASS if i am doing this on the production screeps server? Not
sure where the keys you are referring to are
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#70 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AFZshRYyMQsb312qfEIzDWnyEYZb0uUZks5svTZygaJpZM4PV_z9>
.
|
@resir014 worked thank you so much |
@wolffman122 You're welcome! I'm going to close this issue later since the issues here are mostly trivial and can be fixed by improving the documentation. It's not perfect, but I'm open for improvements to the docs. |
The latest build has errors helped people on slack with the version from 9/14 and works fine. |
Confirmed working as per the Slack discussion earlier. Closing this now. |
I can probably figure this out myself, however I could not see any answers to this on the supplied wiki and guides.
(It's pretty late at night, so I'm not in the mood to fully debug)
I believe that tslint, webpack, etc are not command that the command line can run:
Here is my npm-debug.log:
The text was updated successfully, but these errors were encountered: