max-mapper / max-mapper/requirebin
make package.json editable, especially for version numbers
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 389
- Forks
- 73
- PR merge metrics
- No merged PRs in 30d
Description
when you first save to a gist requirebin creates a package.json for you w/ the versions pegged at the newest version of each module. we should surface this in the UI so that people can edit it in order to upgrade to newer versions of modules
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 inspecting the UI flow used when a gist is first saved and the code that creates its package.json. Determine where that generated file can be surfaced for editing; done means users can change module version numbers in the UI and save those changes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100