Mucks up directory structure when creating tmp dir, can't find file

[DustinDSchultz]

My require looks like this:

require('typescript-require')({
    nodeLib: '../../app/typings/index.d.ts',
    targetES5: true,
    exitOnError: false
});

var LoginController = require('../../app/features/login/loginController.ts').LoginController;

But I get this error:

Error: ENOENT: no such file or directory, open '/Users/DSchultz/projects/hcp-portal/tmp/tsreq/app/features/login/loginController.js'

When I investigate what that directory looks like ...

ls tmp/tsreq/app/features/login/

I get these two subdirectories:

config   features

If I follow them down further I see that the file location is actually tmp/tsreq/app/features/login/features/login/loginController.js.

[DustinDSchultz]

I've confirmed that reproducing the node tsc.js command in the command line produces the same results.

tsc --nolib --target ES5 --module commonjs --outDir /Users/DSchultz/projects/hcp-portal/tmp/tsreq/app/features/login /Users/DSchultz/projects/hcp-portal/node_modules/typescript/lib/lib.d.ts /Users/DSchultz/projects/hcp-portal/node_modules/typescript-require/typings/node.d.ts /Users/DSchultz/projects/hcp-portal/app/features/login/loginController.ts

Creates the extra directory structure as well. Weird.

[DustinDSchultz]

Looks like the npm package is behind the current state of the project. If I clone the project instead of npm installing it there are no issues.

[DustinDSchultz]

Hehe, turns out I had generated the files after fixing some stuff in code, and once that was done one time they existed and were no longer the cause of any errors...so the problem is still here!

I've forked the project and fixed the issue by using tsc's "rootDir" property. I've set it to process.cwd() and changed the "outDir" to tmpDir and it seems to work great. Before I make a pull request I'd like to test it against some existing projects.