Closed kaicataldo closed 2 years ago
What's the usecase for this / where Git-ignoring lockfiles is not enough?
Allowing the creation of lockfiles could lead to a local npm install
respecting package-lock.json
, making the local dev environment different from CI. It would be caught in CI, so not a huge deal, but might help save some time/confusion. If this isn't something you think is useful, please feel free to close the PR :)
where Git-ignoring lockfiles is not enough?
The only place is CI that caches artifacts. Using npmrc is considered "proper" for this reason.
I noticed that this repo doesn't include a lockfile but doesn't have
.npmrc
preventing the lockfile from being created. Figured I could make a quick PR :)