Closed fuentesjr closed 8 years ago
This problem will be fixed once you upgrade to npm 3. Upgrade by running npm install -g npm@next
. Let me know whether it resolves your problem?
@somus Yup, that was the issue. Thank you sir. I'll go ahead and close this issue now. By the way, was this relatively obvious?