-
Notifications
You must be signed in to change notification settings - Fork 521
npm Dependencies #119
Comments
You're totally right - the version of NPM that VS2015 uses by default is 2.x which doesn't work properly on Windows. You can upgrade to a newer version of NPM manually, or hassle the VS people to ship an update that includes NPM 3.x. Closing as there's nothing we can do here - it's a VS issue. |
Thanks for explaining I had no idea they were bundled. I've upvoted the use of external node/npm/bower implementations. I can see the advantage of bundling with VS initially but the inevitable inconsistency is really unfriendly. |
Just FYI, if you have npm installed on your machine you can tell Visual Studio to use it instead by
|
@JonCubed Thank you, I should have spotted that. I have tried that but unfortunately I am still stuck on "Dependencies - Not Installed". npm version is 3.8.3. |
@simonwoodhead have you tried right-click _Dependencies - Not Installed_ and selecting Restore packages ? You could also try modifying the packages.json and on save it should restore them |
@JonCubed I also tried the "Configure external tools" workaround, but am still seeing " - not installed". I have npm 3.9.3. I tried everything short of restarting my computer. @simonwoodhead, did you get yours resolved? |
Sadly not. On Mon, 20 Jun 2016 19:17 Tony, notifications@github.com wrote:
|
@simonwoodhead @antmdvs when I upgraded to preview 1, I am now also seeing it but the packages are being downloaded, I can see them all listed under the npm folder. I also ran |
@simonwoodhead @antmdvs you can track the issue at aspnet/Tooling#479 |
Not a major issue but the Dependencies folder in Visual Studio 2015 does not play nicely with these templates. It says "Dependencies - not installed" (when in fact they are) and right-click > Restore Packages restores packages but changes back to "Dependencies - not installed" when it is complete. The ASP.NET Core Web Application template that is built into Visual Studio 2015 doesn't have this problem (but then it doesn't have React or Webpack!).
The text was updated successfully, but these errors were encountered: