Fix/issue support tsconfig extends

[mrseanryan]

Adds support for "extends" property in the tsconfig.json, so the relevant properties are read from base configs as appropriate (via TypeScript).

Internal: uses absolute paths which is less ambiguous in case a project has different types with same local paths.

---

A continuation of #200 (mainly due to Travis issue)

Possibly would solve #102

---

• [x] add itest that shows extends is not working
• [x] add proper support for extends ('paths')
• [x] add support for reading baseUrl from extends

ref = https://github.com/microsoft/TypeScript/issues/18865 ref = https://npm.io/search/keyword:tsconfig

[mrseanryan]

update:

• simple fix, which reads 'paths' from the result of ts.parseJsonConfigFileContent() instead of the raw value

TECH DEBT: we don't read baseUrl from the result - so probably that is also a bug?

[mrseanryan]

• [x] Try to properly support baseUrl

[boredland]

really nice you followed up with this!

[mrseanryan]

@boredland this PR supports baseUrl reading, even when 'extends' is in use. If you have time to try it out, that would be great!

@pzavolinsky this is a major change, but I believe a good improvement.

Internally it is a bit simpler (just 'baseUrl' - baseDir and rootDir are no more - I always found it hard to differentiate them anyway....) It should solve some issues for projects that use base tsconfig files (via 'extends').

[mrseanryan]

@pzavolinsky it seems a bit difficult to get PRs merged such as this one...

Perhaps automating the build could help - ref #208 or #48

[andrewbihl]

What's the status here? I'd like to use this without forking

[mrseanryan]

Only @pzavolinsky has access to fix the build + release to npm.

[pzavolinsky]

Sorry I've been out for so long. We need to do some clean up and fix CI, in the meantime, @mrseanryan if you can merge latest to master, I'll release manually.

[mrseanryan]

@pzavolinsky its merged! thank you

[pzavolinsky]

Released as 8.0.0, sorry for the long wait!