Presence of a common ancestor path for files makes gulp-ts unable to find resulting files

[RoystonS]

The TypeScript compiler has some 'helpful' behaviour in that it tries to guess a common ancestor directory for source files in order to produce shorter output paths.

That is, if you ask it to compile the following files in one go:

src/pkg1/File1.ts
src/pkg2/File2.ts

it guesses that the common path prefix is 'src/', and so if asked to generate into a directory named 'output', it generates files

output/pkg1/File1.js
output/pkg2/File2.js

gulp-ts, however, doesn't take this common ancestor detection into account, and looks for

output/src/pkg1/File1.js
output/src/pkg2/File2.js

These don't exist, so gulp-ts errors when it's trying to find TSC's generated output.

gulp-ts could either perform a similar common ancestor detection or the files could be located by repeated existence testing and removal of directory prefixes. (i.e. check first for output/src/pkg1/File.js, then output/pkg1/File.js, ...)

(I also wonder if this is in some way related to issue #2 ?)

[activescott]

I've observed the same behavior. I believe this is similar to the test 'should work with a file in subfolder only' in the test.js file. In that test it removes the subfolder for the single file, which is slightly different but is similar "guess behavior" where it's shortening unnecessary output paths. I suggest creating a test there for this specific case to help instigate a fix.

[panuhorsmalahti]

This seems to fail even if you compile just one file, e.g.

lib/foo.ts

Typescript compiles to 'compilerdir/foo.js', but gulp-ts tries to read from 'compiledir/lib/foo.js'.

This could be fixed by first checking if TypeScript is trying to guess/flatten the output folder, and if so, read the output file from the flattened path.