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

Update tsconfig.json for Typescript 1.6 #78

Merged
merged 1 commit into from
Sep 21, 2015
Merged

Conversation

jimthedev
Copy link
Contributor

Update the version of the tsconfig.json to match the TypeScript version
in package.json and fixes the path to lib.dom.d.ts which moved as of TS
version 1.6

This fixes annoying red squiggly line errors in visual studio code (and potentially
other editors) relating to module, experimentalDecorators or emitDecoratorMetadata
not being set.

Update the version of the tsconfig.json to match the TypeScript version
in package.json and fixes the path to lib.dom.d.ts which moved as of TS
version 1.6

This fixes annoying red squiggly line errors in visual studio code (and potentially
other editors) relating to module, experimentalDecorators or emitDecoratorMetadata
not being set.
@jimthedev
Copy link
Contributor Author

This is all set. /cc @gdi2290

@PatrickJS
Copy link
Owner

thanks!

PatrickJS added a commit that referenced this pull request Sep 21, 2015
Update tsconfig.json for Typescript 1.6
@PatrickJS PatrickJS merged commit ed98f2a into master Sep 21, 2015
@jimthedev jimthedev deleted the jimthedev-patch-1 branch September 21, 2015 06:13
@PatrickJS
Copy link
Owner

(just found out the version number was only added for atom support and the tsconfig spec has no mention of a version field)

@jimthedev
Copy link
Contributor Author

Weird. I saw it in there but no one I talked to had heard of it. Does atom still require it?

@jimthedev
Copy link
Contributor Author

I do wish Visual Studio Code would not silently ignore tsconfig.json when a file path is wrong in the 'files' array. Seems like skipping that file might be more sensible.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants