3 ms·
looking forward to updating more .gitignores with 3 of these 4 package-lock.json yarn.lock deno.lock bun.lock
by culi 2y ago
looking forward to updating more .gitignores with 3 of these 4
package-lock.json
yarn.lock
deno.lock
bun.lock
- conradludgate 2y agoWhy would you gitignore those? Adding lockfiles to git repositories is considered good practice
- Cthulhu_ 2y agoAnd why would they use multiple competing package managers and runtimes? It isn't a good faith comment.
- diggan 2y ago> And why would they use multiple competing package managers and runtimes? Some of us work across multiple projects and aren't up in our arms about what package manager the current project use. Some days you touch 3-4 projects that happen to all use different package managers.
- phinnaeus 2y agoIt’s not just good practice it’s the whole point
- culi 2y agoI said 3 out of 4 of these. Committing multiple lockfiles is not good practice but I see people that struggle with the idea that package managers are not interchangeable all the time
- Etheryte 2y agoSurely you would enforce this at pull request time, no? Ignoring the file works from a functional perspective, yes, but does nothing to solve the actual problem.
- culi 2y agothe "actual problem" is often management trying to find cheap labor or even using AI to "do it themselves"
- 5Qn8mNbc2FNCiVV 2y agoIf someone commits a wrong lockfile they are fired where I work at lol (exaggerating, but only slightly)
- sampullman 2y agoCan't forget pnpm-lock.yaml ;)
- culi 2y agoI use pnpm the most and I missed this :O
- hamandcheese 2y agoThis is an underrated and misunderstood comment. Let me explain: projects usually support only one package manager. In a world of N competing JS package managers, you need to ban lock files from N-1 of them.