Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[1.7.0] ng serve not properly killed on CTRL+C with yarn/npm

See original GitHub issue

Versions

Angular CLI: 1.7.0
Node: 6.9.5
OS: linux x64
Angular: 5.2.5
... animations, common, compiler, compiler-cli, core, forms
... http, language-service, platform-browser
... platform-browser-dynamic, router

@angular/cli: 1.7.0
@angular-devkit/build-optimizer: 0.3.1
@angular-devkit/core: 0.3.1
@angular-devkit/schematics: 0.3.1
@ngtools/json-schema: 1.2.0
@ngtools/webpack: 1.10.0
@schematics/angular: 0.3.1
@schematics/package-update: 0.3.1
typescript: 2.5.3
webpack: 3.11.0

Repro steps

create project with ng new
run yarn start or npm start
hit ctrl-c

Observed behavior

the ng process is still running

Desired behavior

The ng process should be stopped. It is stopped with v1.6.8 but not with v1.7.0

Mention any other details that might be useful (optional)

It happens also with node 8, with yarn or npm. The version of those did not change: only switching between v1.6.8 and v1.7.0 exhibits the problem.

When running ng serve by hand, surprisingly hitting ctrl+c does not stop the ng process, but you have to hit ctrl+c again for it to happen!

Issue Analytics

State:
Created 6 years ago
Reactions:32
Comments:15 (3 by maintainers)

Top GitHub Comments

18reactions

esanzgarcommented, Feb 20, 2018

killall ng

10reactions

athulrejicommented, Feb 17, 2018

Try ctrl + shift + c

Top Results From Across the Web

ng serve --open reports port 4200 is already in use when it isn't

Step 4: Stop your server properly. Don't forget now to close properly your server by using Ctrl + C and typing Y: That's...

Ctrl + C - not killing the process node server - Ionic Cli 4 beta

I'm having issue with ionic 4 serve. By serving project with ionic serve, first time it serves with default port 8100. After ctrl...

Changelog - Cypress Documentation

Fixed an issue with Angular Component Testing where urls within SASS/SCSS files were not being correctly resolved which could result in incomplete styling....

Getting Started — OpenSphere latest documentation

(Not necessary if you followed the yarn instructions above). Clone opensphere, then change directory to the clone. Run npm install .

Bug listing with status RESOLVED with resolution OBSOLETE ...

(was: =dev-java/jdbm-1.0 is available)" status:RESOLVED resolution:OBSOLETE severity:enhancement · Bug:107027 - "dev-vcs/cvsd init script for is not ...