4 ms·
The days before lock files were a thing and 'it works on my machine!' was rampant.
by SenHeng 4y ago
The days before lock files were a thing and 'it works on my machine!' was rampant.
- anitil 4y ago... are we no longer doing 'works on my machine' ?
- coding123 4y agoAt companies that don't check in node_modules, build folders, and are using standard packaging tooling like maven or yarn or npm or what-have-you. Yes, I haven't experienced that in like 15 years.
- dotancohen 4y agoOstensibly if it works in Alice's Docker instance, it will run in Bob's Docker instance too.
- Beltiras 4y agoExcept for weird Docker edge cases (extremely rare, but does happen).
- necovek 4y agoNot rare at all. Docker is a congregation of technologies held together with duct tape and glue. Eg. permissions handling is completely different on Macs with Docker Desktop from the Linux dockerd stuff: on Macs, it automatically translates user ownership for any "mounted" local storage (like your code repository), whereas on Linux user IDs and host system permissions are preserved. Have some developers use Macs and others use Linux, and attempt to do proper permissions setup (otherwise known as "don't run as root"), and you are looking for some fun debugging sessions.
- the_common_man 4y ago> Docker is a congregation of technologies held together with duct tape and glue. No, it's not. What a wild conclusion to reach from the example you gave.
- sigio 4y agoWell... unless some dev's have M1-macs, and some of the docker layers are not available for arm, or the other way around, not available for amd64. Gives interesting issues.
- deleted 4y ago[deleted]
- sausagefeet 4y agoLock files protect you from the version changing out from under you, but modules disappearing from NPM is a thing that happens. Yes, you can use artifactory or similar as a proxy but that requires infrastructure that you may not want to run. That is all to say: there are situations where committing node_modules is the least evil.