-
Notifications
You must be signed in to change notification settings - Fork 44
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
CLI not working #49
Comments
Do you have the npm folder in your path? |
I installed using |
Ok. Still, do you have the npm folder in your path? Can you run any other globally installed npm binary? |
Yep. |
i think this is because |
It works properly on my OSX so I don't think thats the reason. |
Hmm... if you |
Possibly but that wouldn't prevent it from running. Have you tried removing it and installing it again? Is the folder returned by: Does this return anything: |
it's definitely the DOS filetype, seen this happen before in other projects.. the probably introduced by 40623da |
ha!, this problem happened before on mdoc as well :P #18 |
Same here :( |
I get the same thing here, using Powershell on Windows 8.1. Anyone know a version that is working out-of-the-box? I intend to use this on my build server so poking around in files locally is not an option. node .\buildDocs.js SyntaxError: Unexpected token ILLEGAL buildDocs.js:
|
Using node v4.1.0 in OSX v10.11. Not sure what's causing this.
The text was updated successfully, but these errors were encountered: