-
Notifications
You must be signed in to change notification settings - Fork 202
Improve TS 1.5 support. #323
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
Personal Note: |
Note: I think using |
We cannot use ts.parse because of the validation stuff we do. Please raise an issue if there are any other compiler flags you need supported 🌹 |
Thanks! As to why My project structure usually looks something like:
As you can see, my source tree is not rooted at my tsconfig.json. This is intentional because I want my source tree to be just source, not a bunch of tool config files, dependency managed files, etc. Because of this structure, I need a way to tell TypeScript that when it builds One of the advantages of this structure is that it allows my tooling to glob on source. If you were to glob on the root directory, you would have to be sure to ignore all of the dependency managed folders as well as all of the various config files. I find it easier (and cleaner) to just keep all of my source code separate from the project metadata which sits in the root folder. |
Cool. Previously I would just move |
https://github.com/TypeStrong/atom-typescript/blob/master/lib/main/tsconfig/tsconfig.ts#L9
TS 1.5 is now available via
npm install typescript
. Since this plugin now uses that, I believe it is safe to follow-through with that TODO.The text was updated successfully, but these errors were encountered: