Move compilation to use tsconfig.json files instead of hardcoded command lines #88
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently there's one checked in tsconfig.json and it actually has different settings than what is used to compile it for testing - in that it says to use strictNullChecks which it doesn't actually compile under.
Part of my motivation for this is that I use a vim plugin which understands the tsconfig.json and tries to do some checking based on it, and it gets rather confused when the tsconfig is wrong - so this fixes that problem.
I do realize that these configs aren't ideal, but my thinking was to get the organization right, and then we can sort out bits like strictNullChecks, noImplicitAny, etc. which the code might not currently work with.