Verifying two version of a module
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 606
- Forks
- 157
- Avg merge
- 3d 23h
- Merged PRs (30d)
- 3
Description
The Hapi community is moving v16 to LTS, and v17 will be supporting Node 8+. We need to verify both, so we do not break old LTS versions.
This affects shot right now, but more will come.
Contributor guide
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 tracing how citgm verifies module versions and how the current shot configuration is handled. Extend that verification to cover both Hapi v16 and v17, then run the relevant test suite to confirm both versions are checked without breaking existing LTS coverage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100