Perhaps it should say "package(s) not installed" but you get the idea now. For the record, I think this is not intuitive and is a poor UX. That hyphen - is intended to mean something. However, then I realized that Visual Studio wasn't saying that npm wasn't installed, it was saying a dependency in the npm tree below wasn't installed. It also lets you choose the exact version you want and it's very smart. I've used this tool many times with success.
#How to repair visual studio 2015 on windows 10 install
npm install -global -production npm-windows-upgrade Just to make sure you have the version of npm you want, Felix made a VERY useful npm-windows-upgrade utility that you run like this, ironically with npm. This looks OK as two of those npms are shell scripts and not run on Windows. C:\Users\scott>where npmĬ:\Users\scott\AppData\Roaming\npm\npm.cmd Side note: WHERE is super useful and not used as often as it should be by y'all. I also ran "where" to see where (and how many) npm was installed. I dropped out to the command line and ran: C:\Users\scott>npm -version That's weird, since I have npm installed. Some of the JavaScript tool libraries didn't load so I went back into Solution Explorer to see if there was a problem and I saw this weird error that said (or at least, I read it as) "npm not installed." Maria and I were doing some work together on Thursday and I did a clone of one of her ASP.NET Core repositories and opened it in Visual Studio 2015 Community Edition on my local machine.
0 kommentar(er)
