Javascriptservices: Visual Studio 2015 shows Dependencies - not installed

[leontyr]

Within it, there is npm - not installed.

When I run npm i, I see the following

npm WARN optional Skipping failed optional dependency /chokidar/fsevents:
npm WARN notsup Not compatible with your operating system or architecture: [email protected]
npm WARN [email protected] No repository field.
npm WARN [email protected] No license field.

[SteveSandersonMS]

The fsevents warning isn't a problem. It's an optional dependency and isn't needed for this to work on Windows.

Are you seeing any other problems? Please reopen with details if so!

[leontyr]

@SteveSandersonMS fsevents is not the issue. The issue is Visual Studio 2015 shows Dependencies - not installed although it might just be a UI problem.

[nil4]

@SteveSandersonMS to add to what @leontyr said: VS shows _Dependencies - not installed_ without any indication of _what_ failed to install. Perhaps this belongs in the aspnet/Tooling repo, though.

[jongalloway]

I'm getting this, too.

1. Scaffold a new application using yo aspnetcore-spa, use any of the templates.
2. Restore and run in console. Opens fine in VS Code.
3. Open the xproj in Visual Studio 2015.
4. Following is displayed in Visual Studio - Solution Explorer:

[pwdst]

Is this related to https://github.com/aspnet/Tooling/issues/479 - gulp-watch seems to be frequently cited as the source of the warning.
Original issue with NPM is at https://github.com/npm/npm/issues/11632

[MarkPieszak]

I think so, that might ultimately be the culprit (or one of the issues) it's definitely not the repo but vstudio

[thesmallbang]

Is there any way to get visual studio to run the install with the --no-optional flag? I assume this would stop the issue we are having with fsevents.

[JonCubed]

Scott Hanselman posted about this recently with a fix
http://www.hanselman.com/blog/VisualStudio2015FixingDependenciesNpmNotInstalledFromFseventsWithNodeOnWindows.aspx

[xperiandri]

That fix does not work for me
Tried with Node.js 3.10.8

[agilehobo]

That fix doesn't work for me too.
Tried with Node.js 3.10.9

[duongthaiha]

Same with be Node.js 3.10.9 still have issues

[SteveSandersonMS]

Sorry to hear you're all still having trouble with that.

This is not the best place to report it - if it bothers you, could you please report it to Visual Studio instead? For example, here. Please bear in mind that this issue is not specific to anything in JavaScriptServices - it applies to _any_ project that takes an NPM dependency on something like angular2 which in turn depends on fsevents.