codepath / codepath/nodejs_guides
Things to Know
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 74
- Forks
- 18
- PR merge metrics
- No merged PRs in 30d
Description
- A general dumping ground of unknown unknowns to help new developers avoid pitfalls and expose them to fantastically better perhaps less known things (like looking for packages first)
- node flags like --harmony --use-strict and --v8-options
- There's a package for that
- uncaughtException & the associated gotcha
- Why Node.js
- ...
- ...
What success looks like: Succinctness and clarity. Less is more.
Reference Wikis: Authentication & Authorization, Setup
Open separate issues for required links to community sources if you're having trouble finding any.
Please assign to yourself before working on this.
/cc @NinjaSudo @philster @azoff @DiyahM
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 reviewing the issue's existing guide content and the referenced Authentication & Authorization and Setup wikis. Define a focused set of pitfalls and Node.js resources before making changes; done means the resulting material is succinct and clear, with any missing community links handled in separate issues.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100