Include package-lock with examples
Open
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 58
- Forks
- 41
- Avg merge
- 2h 7m
- Merged PRs (30d)
- 3
Description
By including the package-lock the initial installs from marko-create will be faster.
Before we do this though we should write a periodic github action that updates the lock files or use green-keeper/whatever.
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
Start by inspecting the example package manifests and the install path used by marko-create. Decide how the package-lock files should be maintained, then verify that each example includes its lock file and that a periodic GitHub Action updates them consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, javascript, node.js
- Domain
- ci-cd, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100