beautifier/js-beautify

Add "--debug" option to enable generating debugging output

Open

#1,372 opened on Apr 10, 2018

View on GitHub
 (3 comments) (0 reactions) (0 assignees)JavaScript (8,342 stars) (1,460 forks)batch import
good first issuetype: enhancement

Description

Currently, the only way to analyze beautification issues is to load up a debugger and step through the code to figure out where the issue is. Having the ability to specify a mode where debugging output could be logged either during or after a run would make analyzing failures faster.

This issues is meant only to add the option and the basic facilities not to add all eventual debug output to the codebase.

Contributor guide

Tech stack
javascript
Domain
cli
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
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.
mostly clear
Prerequisites
basic JavaScriptcommand line argument parsing
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60
Research direction
Investigate the CLI entry point (likely lib/cli.js or index.js) to understand how arguments are currently parsed, e.g., using yargs or minimist. Look for existing option handling patterns to add a ' debug' flag. Consider where to inject debug logging, such as a global debug variable or a logger module. Review similar features in other beautifiers for reference.
Add "--debug" option to enable generating debugging output · beautifier/js-beautify#1372 | Good First Issue