We Put Half a Million Files in One Git Repository, Here’s What We Learned

Re:We Put Half a Million Files in One Git Repository, Here’s... by diegoveralli on Thursday June 16, 2022 @05:30AM (#31764051)

Npm didn't support lockfiles until version 5, released in 2017, Yarn had them at launch in 2016. Before that committing node_modules was often used as a form of vendoring, to get reproducible builds.

If a new project these days commits node_modules to git, it's likely a mistake, but for legacy projects started before 2017 it was the lesser of two evils.

Edit: spelling.

[ Parent | on HN ]

Re:We Put Half a Million Files in One Git Repository, Here’s... by jamesfinlayson on Thursday June 16, 2022 @08:09PM (#31772532)

Hm, this project was started in 2017. The node_modules directory was for Serverless (a tool written in Javascript), not the website itself (which was written in AngularJS - probably not the best choice in 2017 either).

[ Parent | on HN ]

Re:We Put Half a Million Files in One Git Repository, Here’s... by Groxx on Thursday June 16, 2022 @01:20PM (#31768594)

s/was often used as a/was the only practical/

Prior to lock files (and potentially after, as checked-in files are beyond trivial to modify and review and that can be worthwhile) committing dependencies in some form was basically the only reasonable way to have reproducible builds, unless you wanted to build your own package manager / lock file implementation.

Which is what Yarn did.

[ Parent | on HN ]