-
Notifications
You must be signed in to change notification settings - Fork 12.8k
VS 2017 RC solution analysis does not respect tsconfig.json "types" property (shows errors) #12330
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
Comments
UPDATE removing the following line from
however that enables global inclusion of all |
removing |
well.. typeRoots were empty so not types were inferred. so the behavior you are seeing is correct. please see www.typescriptlang.org/docs/handbook/tsconfig-json.html#types-typeroots-and-types for more details. |
i explicitly had the only vs 2017 built-in solution analysis chokes. but if you are fine with functional discrepancies, okay i guess. |
We should look why there is a difference in behavior there. but this configuration does not look right. you are saying include |
from what I understand, by default the compiler will include all all definitions explicitly loaded in code are loaded normally regardless. so my project has type definitions for |
this is not accurate. all declaration files under |
TypeScript Version: VS 2017 RC, Community Edition
Code
open a project that uses the tsconfig.json "types" property, such as
and vs 2017 RC shows errors such as
Expected behavior:
tsc
compiles the project fine. also opening the project in VS2015 with NodeJs tools works fine.Actual behavior:
vs 2017 RC shows intellisense errors in the error list. building
ctrl-shift-b
works fine and no errors are shown.Repo Steps*
download the
xlib
project from https://github.com/Novaleaf/xlib and open it in VS2017 RC Community Edition.The text was updated successfully, but these errors were encountered: