We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Angular CLI: 1.7.0 Node: 8.9.3 OS: darwin 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.6.2 webpack: 3.11.0
ng new --skip-install -sg -it my-app && cd my-app yarn install yarn start --aot --open CTRL+C
When executing locally installed ng via npm start or yarn start
ng
npm start
yarn start
Server is not terminated and keeps running. Extensive hunt for hanging Node PID is needed, followed by killing the process with kill PID ouch!
kill PID
when server is run via globally installed ng it is killed as expected....
When yarn ng serve is terminated, it should be properly terminated
yarn ng serve
The text was updated successfully, but these errors were encountered:
Duplicate of #9647
Sorry, something went wrong.
Closing as duplicate of #9647.
This issue has been automatically locked due to inactivity. Please file a new issue if you are encountering a similar or related problem.
Read more about our automatic conversation locking policy.
This action has been performed automatically by a bot.
No branches or pull requests
Versions
Repro steps
Observed behavior
When executing locally installed
ng
vianpm start
oryarn start
Server is not terminated and keeps running. Extensive hunt for hanging Node PID is needed, followed by killing the process with
kill PID
ouch!when server is run via globally installed
ng
it is killed as expected....Desired behavior
When
yarn ng serve
is terminated, it should be properly terminatedMention any other details that might be useful (optional)
The text was updated successfully, but these errors were encountered: