mysticatea/npm-run-all

Parallel tasks can't be killed in Webstorm Terminal on Windows

Open

#33 opened on Mar 24, 2016

View on GitHub
 (14 comments) (3 reactions) (0 assignees)JavaScript (5,484 stars) (271 forks)batch import
bugevaluatinghelp wanted

Description

This is admittedly Webstorm specific, but as FYI:

This is the same issue that I reported in Issue 32, but it occurs in Webstorm's terminal on Windows. Hitting Ctrl+C produces the prompt for "Terminate batch job (Y/N)?", but answering "Y" doesn't actually get you back a usable command line. It appears to be using the native Window command line behind the scenes since this is shown when I open the Webstorm terminal:

Microsoft Windows [Version 6.1.7601] Copyright (c) 2009 Microsoft Corporation. All rights reserved.

The result of hitting Ctrl+C: ^C^C^CTerminate batch job (Y/N)? Terminate batch job (Y/N)? ^CTerminate batch job (Y/N)? ^^CCTerminate batch job (Y/N)? Terminate batch job (Y/N)? Terminate batch job (Y/N)? ^CTerminate batch job (Y/N)? Terminate batch job (Y/N)? Y

It becomes frozen after answering Y.

Contributor guide

Tech stack
javascriptnodejs
Domain
clideveloper experience
Issue type
bug
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.
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
Node.js basicsWindows OSProcess signals familiarity
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
35
Research direction
Start by examining the signal handling in the npm run all source code, likely in the `src/` directory, focusing on how child processes are spawned and terminated. Review the comments in the issue for any suggested workarounds or fixes. Test the behavior in Webstorm on Windows and compare with other terminals. Consider using Node.js `process.on('SIGINT')` and child process spawn options for Windows compatibility.