Skip to content
This repository was archived by the owner on Aug 7, 2021. It is now read-only.

fix: show message for stopping webpack only when it has been started #821

Merged
merged 1 commit into from
Mar 11, 2019

Conversation

rosen-vladimirov
Copy link
Contributor

Currently the message Stopping webpack watch is printed whenever CLI executes after-watch hooks, i.e. when user runs tns run <platform> and sends Ctrl+C, the message is shown. However, we have not started any webpack process, so there's nothing to stop.
Print the message only when webpack process had been started. Also print it only when --log trace is used.

PR Checklist

What is the current behavior?

Message Stopping webpack watch is shown when you execute tns run <platform> (without --bundle) and press Ctrl + C.

What is the new behavior?

Message Stopping webpack watch is shown only when you execute tns run <platform> --bundle and press Ctrl + C.

Fixes/Implements/Closes #[Issue Number].

Currently the message `Stopping webpack watch` is printed whenever CLI executes `after-watch` hooks, i.e. when user runs `tns run <platform>` and sends Ctrl+C, the message is shown. However, we have not started any webpack process, so there's nothing to stop.
Print the message only when webpack process had been started. Also print it only when `--log trace` is used.
@rosen-vladimirov rosen-vladimirov self-assigned this Feb 25, 2019
@rosen-vladimirov
Copy link
Contributor Author

test package_version#latest

@etabakov
Copy link
Contributor

@cla-bot check

@cla-bot cla-bot bot added the cla: yes label Feb 25, 2019
@cla-bot
Copy link

cla-bot bot commented Feb 25, 2019

The cla-bot has been summoned, and re-checked this pull request!

@rosen-vladimirov rosen-vladimirov merged commit 1bd18e5 into release Mar 11, 2019
@rosen-vladimirov rosen-vladimirov deleted the vladimirov/trace-messages branch March 11, 2019 10:45
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants