Package maintenance or transfer npm pkg?
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Hi @manosim,
First thanks very much for creating this component, and I tried it in my own project several days ago, but then I found it just could not work correctly.
It seems that it's out of maintenance about 4 years, and the source code is outdated.
So my question here is, if you don't mind and don't want to maintain this package anymore, would you like to transfer the ownership of npm package? Its package name is nice and it would be great to let it be reborn and benefit the community.
My apologize for any rude requests.
Best wishes.
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 concerns transferring ownership of the npm package for this React component, but names no source files, tests, or entry points. A maintainer must first decide whether to transfer the package; done would be a maintainer response and, if approved, completion of the transfer.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, react
- Domain
- release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 10/100