vadimdemedes/gifi

Handle npm errors.

Open

#28 opened on Apr 27, 2016

View on GitHub
 (3 comments) (0 reactions) (0 assignees)JavaScript (1,025 stars) (42 forks)batch import
enhancementhelp wanted

Description

Had a syntax error in a package.json. Took a few tries to realize I had the error with packages not downloading. Would be nice if Gifi printed out that error when it happens instead of just exiting with no message.

Contributor guide

Tech stack
nodejs
Domain
developer experiencetooling
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.
mostly clear
Prerequisites
JavaScriptNode.js child process
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70
Research direction
The issue requests that gifi display npm error messages when npm install fails due to package.json syntax errors. Investigate how gifi currently spawns npm (likely using child process.spawn or exec) and capture stderr output. Modify the relevant file (probably index.js or a similar entry point) to print any error output from npm to the console before exiting. Consider using the 'exit' event or checking the stderr buffer. The existing comments may provide hints.