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

compileOnSave with TS 2.0.2 still not working properly #10838

Closed
kr4uzi opened this issue Sep 10, 2016 · 2 comments
Closed

compileOnSave with TS 2.0.2 still not working properly #10838

kr4uzi opened this issue Sep 10, 2016 · 2 comments
Labels
Unactionable There isn't something we can do with this issue

Comments

@kr4uzi
Copy link

kr4uzi commented Sep 10, 2016

TypeScript Version: 2.0.2

Code
ts-files in (project root\wwwroot)
tsconfig.json (project root):

{
    compileOnSave: true,
    compilerOptions: {
        // ...
    }
}

Expected behavior:
compiles when i hit CTRL + S
Actual behavior:
does not compile (only when i hit BUILD explicitly)

on a system with a similar configuration (both vs2015 with latest patches and ts 2.0.2) it works as expected so this feature is still not working properly. the typescript folder (program files x86\MS SDK...\Typescript is added to %PATH% in both systems).

@zhengbli
Copy link
Contributor

zhengbli commented Sep 10, 2016

The compile-on-save on tsserver is not released yet. Though I'm confused as you said "similar configuration works as expected"? Then what is the difference in your setup?

@kr4uzi
Copy link
Author

kr4uzi commented Sep 11, 2016

the difference is that one setup was dedicated purly on web-dev (the one where its not working) and the other one was rather focused on driver-dev (driver dev kits and c++ env installed). However as the former was running in a VM i just reseted it and reinstalled VS (discovered some problems with uninstalling the net core tools maybe this was what caused problems actually).
Its working as expected now. However that comile on save feature is defenitly not consistently working because on my "driver-dev" machine it didnt work out of the box either (as many other users with the same problem state: it just started working magically).
Not sure if its reasonable to let this issue remain open now, as its working, but there is defenitly some unwanted magic happening...

@RyanCavanaugh RyanCavanaugh added Needs Investigation This issue needs a team member to investigate its status. and removed Needs Investigation This issue needs a team member to investigate its status. labels May 24, 2017
@RyanCavanaugh RyanCavanaugh added Unactionable There isn't something we can do with this issue and removed Needs Investigation This issue needs a team member to investigate its status. labels Sep 20, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Unactionable There isn't something we can do with this issue
Projects
None yet
Development

No branches or pull requests

3 participants