swagger-api / swagger-api/swagger-client
Remove `@scarf/scarf` dependency
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 2.7k
- Forks
- 765
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 6
Description
Same as https://github.com/swagger-api/swagger-ui/issues/10573 but for this repo. Users of strict package managers like pnpm >= 10 will never run this analytics so it's a inaccurate deadweight and should be removed.
Given that swagger-js is a dependency of swagger-ui, it should be done here first, then released and full removal done in swagger-ui with that update.
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 locating the repository's package manifest and any dependency metadata that references @scarf/scarf. Check how the package is installed and tested, then verify the dependency is removed from the published package metadata without breaking the existing checks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- tooling
- Issue type
- Refactor
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 70/100