pnpm has had a lockfile for quite some time. It is called shrinkwrap.yaml. I just updated it to have additional fields. See pnpm@0.69.1
-
-
It's just a bikeshed. Call it "xyz.fooblz" and it'd be fine, as long as it's communicated well enough to become a community idiom.
-
Words are just tokens in the language game. Semantics are the outcome of the moves in that game. They come from the players, not the pieces.
-
And .lock is a hugely popular, cross-language idiom for package management. ;)
-
Other than rubygems and package managers you wrote?
-
Don't get me wrong, you're hugely influential. But so are maven, pear, cpan, nuget, npm, et al, where *.lock means "fs mutex"
-
Ah! Composer uses a .lock file, as well.
-
Also pub, cocoapods. It's not limited to package managers I personally had a direct hand in.
-
I don't feel strongly about it because it was my idea (I admit that it was arbitrary initially) but at this point it's the dominant idiom.
- 4 more replies
New conversation -
-
-
.json was literally just the laziest alternative. We figured as long as people had 'lock' in the name, it'd be fine.
-
I don't particularly care for .lock because it doesn't clue in tools about how to highlight/parse the file. But that's not a *huge* deal, no
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
