-
Notifications
You must be signed in to change notification settings - Fork 12.6k
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
Visual Studio 2017 is compiling JS file without associated TS file #14827
Comments
Thanks. I just tried this and couldn't repro, then realized I was running TypeScript 2.2. Switching to 2.1 (that comes with VS 2017) I could repro. If you could try using TypeScript 2.2 (as outlined in #14529 (comment) ) and confirm this fixes the issue, at least we'll know this is already addressed somehow (I couldn't spot the exact commit which would have fixed it). |
I haven't got around to testing this but is there a new version of TypeScript going to be released with a 2017 update? |
I just realized I went ahead and tried to reproduce with the latest Visual Studio released May 10, 2017 - version 15.2 (26430.04). Without any changes to |
Thanks for confirming it's fixed in the latest release. |
@billti I just had this happen to me again today. I am using Version 15.2 (26430.6) now. |
Is this supposed to be fixed with selecting TypeScript 2.1 or only in 2.2? |
Im on 2.3.3 and it is happening to me also |
TypeScript Version: 2.1.5
Code
Get master branch from here:
https://github.com/styfle/TypeScriptReproBug
Expected behavior:
Do not compile
.js
files if there is no matching.ts
file.Actual behavior:
The
.js
files are modified and a.js.map
file is generated.More Info
I opened an existing 2015 project in VS 2017, edited a
.d.ts
file, saved, and VS started compiling a lot of files....files that do not have a.ts
associated with them 😨Then I looked at git changes in Team Explorer tab and I can see that a bunch of
.js
files were modified and a bunch of.js.map
files were added.@billti Please review the code. Thanks!
The text was updated successfully, but these errors were encountered: