publish
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- javascript, react
- Domain
- release
Research direction
Compare the published npm package with the master branch, focusing on whether onChange is present in the release. Then inspect the repository's publishing entry point and verify that a new publication includes the missing behavior and matches master.
Written by the indexing model from the issue text.
Description
the version published to npm does not match master. in particular onChange didn't make it into the release, and that would be super useful.
- Dominant language
- JavaScript
- Stars
- 97
- Forks
- 38
- PR merge metrics
- No merged PRs in 30d
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.
More from arqex/react-json
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
arqex/react-json#11 · 1 comment ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
arqex/react-json#9 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 20/100
arqex/react-json#7 · 9 comments ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
arqex/react-json#5 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 30/100
arqex/react-json#3 · 1 comment ·
All issues in arqex/react-json
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
HarperFast/skills#96 ·
-
[Block] Latest Posts [Type] Bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Automattic/studio#4908 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
sugarlabs/musicblocks#8847 ·