I am having trouble with npm and node version 0.10.40. I never had this problem before and I am not behind a proxy. I have tried other solutions that I found on Stack Overflow and other forums such as changing the registry url to http://.. rather than https://.., and setting strict-ssl to false. When I do this npm is unable to parse JSON. Here is my npm-debug.log. Maybe someone can help me figure out what is going on.
相关问题
- npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fs
- Pass custom debug information to Microsoft bot fra
- google-drive can't get push notifications
- Failed at the electron@1.8.2 postinstall script
- How to reimport module with ES6 import
相关文章
- node连接远程oracle报错
- How can make folder with Firebase Cloud Functions
- @angular-cli install fails with deprecated request
- node.js modify file data stream?
- How do I get to see DbgPrint output from my kernel
- How to resolve hostname to an ip address in node j
- Transactionally writing files in Node.js
- Log to node console or debug during webpack build
Behind corporate firewall setting proxy also does not works ..try this to get it working ..
http://www.sharepointconfig.com/2017/04/using-npm-behind-a-proxy-that-uses-ntlm-authentication/ http://www.sharepointconfig.com/2017/04/using-npm-behind-a-proxy-that-uses-ntlm-authentication/
When you are behind the proxy in a corporate environment you would have used the following commands
When you are not just switch the proxy off by
Best solution is:-
In case your
npm
is unable to build thephantomJS/CasperJS
packages because of network proxy issue, simply download thecasperjs
andphantomjs
manually and add to App_data folder in your C:/ folder.Open your command prompt and execute below code:
Add the
casperJS
andphantomJS
to your PATH variable of your machine.Run the
casperjs
... problem will be resolved.I solved this issue by issuing the following commands
Apparently npm was attempting to bypass a proxy or believed it was behind a proxy. Strange.