semantic-release / semantic-release/gitlab
consider switching from got to ky
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 344
- Forks
- 89
- Avg merge
- 16h 11m
- Merged PRs (30d)
- 4
Description
https://www.npmjs.com/package/ky
from the got readme:
You probably want Ky instead, by the same people. It's smaller, works in the browser too, and is more stable since it's built upon Fetch.
i've used ky in a few projects now and it has been solid. would it make sense to switch here?
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 issue names no files or tests; start by comparing the linked got README with the ky package page, then locate this plugin's current got usage and related tests. Done means the repository has a decided, tested migration path or a documented reason not to switch, including compatibility concerns.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- gitlab, javascript
- Domain
- release
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100