3 ms·
> A new, standardised lockfile feature meant for cross-package-manager compatibility (package-lock.json) Surely it would be much better to follow standard lock
by evolve2k 9y ago
> A new, standardised lockfile feature meant for cross-package-manager compatibility (package-lock.json)
Surely it would be much better to follow standard lock file naming conventions and name the file package.lock
- kuschku 9y agoOr even package.lock.json
- evolve2k 9y agoI had originally been for package.lock, but after reading right through the issue I now agree with your excellent suggestion of package.lock.json. Rather than just talk here, I've posted against the issue suggesting this approach basically asking for up/down votes. https://github.com/npm/npm/pull/16441#issuecomment-304458746 https://github.com/npm/npm/pull/16441#issuecomment-304458746
- deleted 9y ago[deleted]
- mstade 9y agoIt bothers me somewhat that they say this is standardized, but not by whom. Is the idea that Yarn should fall in line or is it a case of https://xkcd.com/927/ https://xkcd.com/927/ ?
- qntmfred 9y agoI'd rather my editor recognize a .json file and treat as such. I don't have a .lock convention