Skip to content
New issue

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

ng serve command changing default integrated terminal in VS Code from 1:cmd to 1:node & stops detecting file changes #8821

Closed
richierich25 opened this issue Dec 10, 2017 · 2 comments
Assignees
Labels
P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent severity2: inconvenient

Comments

@richierich25
Copy link

richierich25 commented Dec 10, 2017

Versions

<!--
Output from: `ng --version`.
If nothing, output from: `node --version` and `npm --version`.
  Windows (7/8/10). Linux (incl. distribution). macOS (El Capitan? Sierra?)
-->
```Angular CLI: 1.6.0
Node: 8.4.0
OS: win32 x64
Angular: 5.1.0
... animations, common, compiler, compiler-cli, core, forms
... http, language-service, platform-browser
... platform-browser-dynamic, router

@angular/cli: 1.6.0
@angular-devkit/build-optimizer: 0.0.35
@angular-devkit/core: 0.0.22
@angular-devkit/schematics: 0.0.41
@ngtools/json-schema: 1.1.0
@ngtools/webpack: 1.9.0
@schematics/angular: 0.1.10
@schematics/schematics: 0.0.10
typescript: 2.4.2
webpack: 3.10.0

<Windows>
Windows 10

<Visual Studio Code>
Version: 1.18.1

### Repro steps
<!--
Simple steps to reproduce this bug.
Please include: commands run, packages added, related code changes.
A link to a sample repo would help too.
-->
* Step 1 From the Integrated Terminal in VS Code (displaying 1: cmd),, Type `ng serve --open`
* Step 2 This serves the application but changes the intetegrated terminal to (1:node)
* Step 3 Any change in files is not detected & webpack stops compiling automatically


### Observed behavior
The Integrated Terminal changes from 1:cmd to 1:node automatically. Also stops detecting changes & never recompiles on saving changes. 


### Desired behavior
<!--
What would like to see implemented? 
The cmd should remain unchanges and should not trigger the node terminal by itself when using ng serve command.
What is the usecase?
What did you expect to see?
-->


### Mention any other details that might be useful (optional)
Although External Terminal is working fine and is able to detect changes as well . Only the integrated terminal is showing an issue.
@Brocco Brocco added severity2: inconvenient P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent labels Dec 11, 2017
@filipesilva
Copy link
Contributor

I'm sorry, I don't know what problem you are experiencing with the VS Code terminals but I don't think it has anything to do with Angular CLI. We don't have any terminal integrations or anything of the sort.

You should open an issue in their issue tracker instead (https://github.com/Microsoft/vscode).

Regarding problems that may cause live reloads to stop working, please check #1610 instead.

@angular-automatic-lock-bot
Copy link

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.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 7, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent severity2: inconvenient
Projects
None yet
Development

No branches or pull requests

3 participants