Luke-warm take: When designating dependencies - use fixed version numbers.
-
Luke-warm take: When designating dependencies - use fixed version numbers. Always. The ability to use things like "3.4.*" is a bug and/or a trap.
Yes, that means you need to update them manually (your tools can help point at them).
But the ability to check out three months old code and not having to guess which version the packages were at that point is a fucking requirement.
-
Luke-warm take: When designating dependencies - use fixed version numbers. Always. The ability to use things like "3.4.*" is a bug and/or a trap.
Yes, that means you need to update them manually (your tools can help point at them).
But the ability to check out three months old code and not having to guess which version the packages were at that point is a fucking requirement.
@tofticles That is a reasonable take if your dependency management tool doesn’t create a lockfile, or you don't commit the lockfile.
-
@tofticles That is a reasonable take if your dependency management tool doesn’t create a lockfile, or you don't commit the lockfile.
@nerdd I do not work with languages that have lockfiles
. -
@nerdd I do not work with languages that have lockfiles
.@tofticles Wellllll…
-
@tofticles Wellllll…
@nerdd Another spicy take: NodeJS, PHP, NPM and JS were all mistakes. 🤪
