Home
Do not avoid checking in nuget or npm packages into source control?
  v3.0 Posted at 26/03/2018 2:53 PM by Lu Zhang
​Reasons for avoiding checking Nuget or Npm packages
  1. Distributed version control systems, such as Git, include full copies of every version of every file within the repository. Binary files that are frequently updated lead to significant bloat and lengthens the time it takes to clone the repository.
  2. When packages are included in the repository, developers are liable to add references directly to package contents on disk rather than referencing packages through NuGet, which can lead to hard-coded path names in the project.

nugetpackages.png  

Figure:  Do not have a folder called "packages" or "Node_Modules" ​


Read more about how to ​omit NuGet packages in source control system​

For better package management , may consider using the Package Management tool in TFS

Related rules

    Do you feel this rule needs an update?

    If you want to be notified when this rule is updated, please enter your email address:

    Comments:

    Note: Social Media login for Yotpo is not working in IE or Safari, please use Chrome. We are waiting for Yotpo to fix it.