react-component / react-component/picker
Versioning: release candidate is labeled as a stable version in npm registry
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 304
- Forks
- 345
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 7
Description
Dear friends, there is an issue with labeling of published packages in npm. I guess the pre-release versions were published as if they are stable versions. It would be nice to fix that so that IDEs would not suggest these versions for update.
Thank you in advance :)
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 package publishing and version metadata used for npm releases. Compare how release-candidate versions are represented in the registry with the intended stable-release behavior, then verify that IDEs no longer treat candidate packages as stable updates.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react, typescript
- Domain
- release
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100