search

aspnet / Tooling

Issue tracker and info on Visual Studio tooling for ASP.NET
Other
256 stars 124 forks source link

package.json IntelliSense doesn't honor .npmrc file settings #246

Open scottaddie opened 8 years ago

scottaddie commented 8 years ago

I often add an .npmrc file at my project root with the following setting:

save-exact=true

By doing so, a specific version of each npm module is installed, and there's no risk of another developer on the team installing a slightly newer minor or major version of the module when running npm install. Unfortunately, the existing npm tooling in VS 2015 now allows developers to bypass that constraint, since the .npmrc file settings don't appear to be honored.

It would be nice if the IntelliSense for package.json didn't display the major and minor versions as options when a setting such as save-exact=true is present in the .npmrc file. In the attached screenshot, I would expect to only see "3.9.0" as an option in the IntelliSense.

semver_npmrc

sayedihashimi commented 8 years ago

TFS: 162791 I've added this to our internal TFS, we will reply back here soon.

webtools-bot commented 7 years ago

The GitHub Issue Tracker for the aspnet/Tooling repo is being deprecated in favor of Visual Studio's Report a Problem tool.

If this issue is still a problem with the RTW release of Visual Studio 2017, please report a new issue using the Report a Problem tool. While you can still use .NET Core and ASP.NET Preview tools with Visual Studio 2015, Visual Studio 2017 is now the officially supported tool for developing .NET Core and ASP.NET Core projects.

By using the Report a Problem tool (available in both VS 2017 and VS 2015), you can collect detailed information about the problem, and send it to Microsoft with just a few button clicks. See Visual Studio's Talk to Us page for more details.

Please use the discussion topic here for feedback and questions on the deprecation of this issue tracker. Thanks!