VS2013 Premium. I attempt to install the NPM package by right clicking NPM in my project. only option not greyed out is install new npm packages. this goes through the download process twice then just sits telling me it is refreshing. If I open the install dialog again we go right back to the beginning.
Once it is finished (Output says download complete) the install new npm packages window has an empty list and states "Catalog Updated Currently refreshing". my desktop and notebook both acting this way, notebook Ive left in this state for 4 hours with no change.
So not only useless but time wasting.
Comments: @ delProfundo Could you please also include the logs from the output window after the dialog has loaded? Even if there aren't any errors, it'll help us figure out what codepath we're running through (https://nodejstools.codeplex.com/wikipage?title=Npm#npm-log-in-output-window ) If any of the packages says "parsing error" - please include a screenshot of the dialog for that package. The errors you saw were coming from npm and look normal (you can verify that you receive similar output if you execute the same npm command in the command line). Note that installation succeeded for 0 and nltk, but not socket. It appears you ran into this issue with socket: http://stackoverflow.com/questions/18652983/unable-to-install-any-module-in-nodejs
Once it is finished (Output says download complete) the install new npm packages window has an empty list and states "Catalog Updated Currently refreshing". my desktop and notebook both acting this way, notebook Ive left in this state for 4 hours with no change.
So not only useless but time wasting.
Comments: @ delProfundo Could you please also include the logs from the output window after the dialog has loaded? Even if there aren't any errors, it'll help us figure out what codepath we're running through (https://nodejstools.codeplex.com/wikipage?title=Npm#npm-log-in-output-window ) If any of the packages says "parsing error" - please include a screenshot of the dialog for that package. The errors you saw were coming from npm and look normal (you can verify that you receive similar output if you execute the same npm command in the command line). Note that installation succeeded for 0 and nltk, but not socket. It appears you ran into this issue with socket: http://stackoverflow.com/questions/18652983/unable-to-install-any-module-in-nodejs