Steve Ognibene

I see. If that is the case, it may be difficult to support other than using the passthrough option. I will have to look into why the TypeScript team decided...

I almost wonder if we need to get into the business of writing out a temporary tsconfig.json file based on the grunt setup, and then essentially always using pass-through. Do...

make tsconfig an object. ``` tsconfig: { tsconfig: './tsconfig.json' passThrough: true } ```

Hi - my sincere apologies on this, but I do not have the time to investigate this. @scriby 's idea sounds good. If you are interested to try to implement,...

Hi, Since you had a `tsconfig.json` you were happy with, just use that. See here: https://github.com/typeStrong/grunt-ts/#tsconfig Basically in the Gruntfile you just need to point grunt-ts to your `tsconfig.json` and...

If you want tsc to use the native `tsconfig.json`, you can just use the passThrough option. For example: ``` javascript grunt.initConfig({ ts: { default: { tsconfig: { passThrough: true }...

There's two simple reasons I can think of that `allowJs` would be passed but not work - one is that you have an older version of TypeScript even though your...

Thanks for this feedback. I will consider it. The trouble is that we intend to support down-level compilers (or even custom ones) in addition to the latest and honestly we...

I looked into this further and I retract my earlier statement. There shouldn't be a backward-compatibility concern. I was thinking we had an existing `rootDir` option, but my memory of...

We did a major rewrite of the documentation a few months ago and it's a lot better than it was, but I agree that this could still be improved. What...