npm dependencies installed via URLs or filepaths are falsely detected as mismatched
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 21
- Forks
- 23
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 17
Description
NPM dependencies may contain version information compliant with semver, but may also contain URLs or file paths in which such information is optional.
https://docs.npmjs.com/cli/v10/configuring-npm/package-json#dependencies
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
No source file, test, or entry point is named in the issue. Start by locating the dependency-mismatch detection and its tests, then read the linked npm package.json dependency documentation to compare semver entries with URL and filepath specifications. Done means URL- and filepath-based dependencies are not falsely reported as mismatched, with regression coverage for those forms.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100