Check in a dependency lock file
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 6.5k
- Forks
- 456
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 5
Description
It's npm's faster, safer cousin.
Lockfiles bring nice predictability in dependencies across multiple node versions as well.
It is basically a drop in replacement for npm as far as devs are concerned.
Edited: npm is prefered over yarn, so the task here is to generate a package-lock.json and check it in.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The requested artifact is package-lock.json. Start by generating it with npm from the repository's dependency manifest, then verify that the lockfile is complete and checked in.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 45/100