max-mapper / max-mapper/maintenance-modules
module creation
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 360
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Description
Some good tips! :+1:
What about module generation suggestions? Using them has definitely improved productivity.
- worth mentioning `npm init` for those unaware
- [mattdesl/module-generator](https://github.com/mattdesl/module-generator), a fork of [hughsk/module-generator](https://github.com/hughsk/module-generator)
- [kewah/npm-module-generator](https://github.com/kewah/npm-module-generator)
- [substack/pkginit](https://github.com/substack/pkginit)
- etc ?
EDIT:
I ended up writing a similar verison of @finnp's create-module, decoupled from scaffolding step:
https://github.com/mattdesl/ghrepo
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
Review the repository's existing module list and its formatting first. Check the npm and module-generator links named in the issue, then compare them with the current entries. Done means the relevant recommendations are represented in the list without broken or duplicate links.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100