better CLI tooling
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 190
- Forks
- 12
- PR merge metrics
- No merged PRs in 30d
Description
- use streams, pipe to stdout unless specified
- ensure that FreeType can be closed without memory leak (for continuous build tools)
- multiple files? globs etc?
- do not console log unless `--verbose` is specified
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
The issue names CLI streams, stdout handling, FreeType cleanup, glob support, and verbose logging, but no files or tests. Start by locating the CLI entry points and the code that opens and closes FreeType; inspect how arguments, output, and logging are currently handled. Done means the requested CLI behaviors are defined and covered by appropriate tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- cli, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100