Do not avoid checking in nuget or npm packages into source control?
26/03/2018 2:53 PM by
Reasons for avoiding checking Nuget or Npm packages
- 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.
- 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.
Do you feel this rule needs an update?