Nicholas Jamieson

[How to Write a Bug Report](https://itnext.io/how-to-write-a-bug-report-3333d8e41efb)

Thanks for opening such a thorough issue. Unfortunately, I don't have the time, at the moment, to figure out why this isn't working for you, but I do have some...

How TypeScript resolves modules - and what it considers to be valid - does not matter. What might matter is how Browserify does it. And what Browserify considers to be...

The environment variable doesn't go into a configuration file; it's specified on the command line, immediately before the command you want to run - as in the doc to which...

The plugin attempts to detect whether or not the host OS has a case-sensitive file system. See https://github.com/TypeStrong/tsify/blob/master/lib/Host.js#L17-L24 If for some reason, this is not working within Docker, I think...

I don't have time to help you debug this and, regardless of that, you've not provided a reproduction of the problem. Generally, bug reports like this are unactionable. tsify's [debug...

As tsify is a plugin, issues like this always involve several moving parts - some version of Browserify, Gulp, etc. On top of that, I've not used tsify lately. I'd...

It's not an option that I've ever used. When using `tsc`, I've always generated the `.d.ts` files beside the `.js` files. And I've never specified with when using tsify. However,...

The `grunt-browserify` `alias` option cannot be supported by `tsify` as it is currently implemented. Said option tweaks the way Browserify resolves modules. However, the TypeScript compilation would need to resolve...

This is not a tsify problem. That package has no available `@types`: ``` $ npm dist-tag ls @types/bandaged__bdapi npm ERR! dist-tag ls Couldn't get dist-tag data for @types/bandaged__bdapi npm ERR!...