Skip to content
This repository has been archived by the owner on Apr 8, 2020. It is now read-only.

npm Dependencies #119

Closed
simonwoodhead opened this issue Jun 8, 2016 · 10 comments
Closed

npm Dependencies #119

simonwoodhead opened this issue Jun 8, 2016 · 10 comments

Comments

@simonwoodhead
Copy link

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!).

@SteveSandersonMS
Copy link
Member

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.

@simonwoodhead
Copy link
Author

simonwoodhead commented Jun 8, 2016

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.

@JonCubed
Copy link

JonCubed commented Jun 9, 2016

Just FYI, if you have npm installed on your machine you can tell Visual Studio to use it instead by

  1. Right-Click _npm_ under Dependencies folder in project tree
  2. Click "Configure external tools..."
  3. Move the nodejs folder (typically c:\Program Files\nodejs) above $(VSINSTALLDIR)\Web\External
  4. Click _OK_ button

@simonwoodhead
Copy link
Author

@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.

@JonCubed
Copy link

JonCubed commented Jun 9, 2016

@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

@antmdvs
Copy link

antmdvs commented Jun 20, 2016

@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?

@simonwoodhead
Copy link
Author

Sadly not.

On Mon, 20 Jun 2016 19:17 Tony, notifications@github.com wrote:

@JonCubed https://github.com/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 https://github.com/simonwoodhead, did you get yours
resolved?


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#119 (comment),
or mute the thread
https://github.com/notifications/unsubscribe/ACKqPu9xoYQJKnx6pP4Jb_LgIvgEahAPks5qNtkrgaJpZM4Iw04L
.

@JonCubed
Copy link

JonCubed commented Jun 21, 2016

@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 npm list --depth 0 in project root and it shows they are installed so think it is a Visual Studio tooling bug

@JonCubed
Copy link

@simonwoodhead @antmdvs you can track the issue at aspnet/Tooling#479

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants