nodejs / nodejs/node-core-utils

Add a verbose option

Open
#467 2 comments 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

feature request
Dominant language
JavaScript
Stars
314
Forks
137
Avg merge
2d 8h
Merged PRs (30d)
24

Description

A few things that come to mind

  1. Show commands spawned by ncu
  2. Show HTTP request response, in particular responses that could not be parsed as JSON (e.g. when Jenkins authorization fails, it returns XML)
  3. Pipe stdout and stderr, also do not use spinners if verbosity is on in case the output is overwritten

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing ncu's command spawning, HTTP response handling, and stdout/stderr or spinner output paths. Add a verbose option covering spawned commands, unparseable HTTP responses, and streamed output without spinners. Done means each requested detail is visible when verbosity is enabled.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
cli
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.