![]() Note the screenshot with the ASCII tree below. I dropped out to the command prompt into to the project's folder and run " npm ls" to see an ASCII tree that effectively is the same tree you see in Visual Studio. I can check the Visual Studio Output Window and I see this: npm WARN install Couldn't install optional dependency: Unsupported Regardless, now I know I can quickly do a string search. I think the "broken" library should also include the BANG (!) or warning icon over it. I started manually opening the tree up one item at a time looking for the bad package - while quietly swearing to myself - until I realized that the Solution Explorer tree nodes are searchable. 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. 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 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |