3 comments (3 comments)6 reactions (6 reactions)0 assignees (0 assignees)JavaScript4,810 stars (4,810 stars)212 forks (212 forks)batch import
help wanted
Description
as in detex file.tex | writegood
Contributor guide
- Tech stack
- javascriptnodejs
- Domain
- cli
- Issue type
- feature
- DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
- 2
- Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
- 1-3 hours
- Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
- stale
- ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
- clear
- Prerequisites
- Understanding of Node.js streamsFamiliarity with write good codebase
- Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
- 85
- Research direction
- Examine the current CLI entry point (likely bin/writegood or similar) to understand how files are read. Look at how other Node.js CLI tools handle stdin, e.g., using through2 or split2. The main code likely processes text from files; modify it to also read from stdin when no files are provided. Check any existing comments for design preferences.