Mohamed Hegazy

```sh c:\test\774>tree /f . │ a.ts │ package.json │ tsconfig.json │ ├───emptyFolder └───node_modules └───@types └───node index.d.ts inspector.d.ts LICENSE package.json README.md c:\test\774>tsc --typeRoots ./emptyFolder --listFiles a.ts C:/Users/mhegazy/AppData/Roaming/npm/node_modules/typescript/lib/lib.d.ts a.ts c:\test\774>tsc --listFiles a.ts...

if i were to guess, you have an `import` somewhere in your file.

Yes. the assumption here is that every subfolder in your typesRoot is a declaration package and not a random folder.

have you tried TS 2.0 with the `@types` packages? see https://github.com/Microsoft/TypeScript-Handbook/blob/master/pages/declaration%20files/Consumption.md

You should not need to specify `typeRoots` if your `node_modules` is on the same level as your `tsconfig.json` is this the case for you? i would say this is an...

types is not if the tsconfig.json is next to your node_modules. i have filed a bug to fix the issue (https://github.com/Microsoft/TypeScript/issues/10617). The compiler does "automatic" inclusion to @types packages; it...

i should add that the intention of the design was not to need to add either. and thus the lack of documentation was under the impression that these references should...

> It seems like this 'magic' behavior should be explained somewhere other than this issue. > In any case, it is now documented here. sure thing. > I am also...

it is explicit. so you need to list `"node_moduels\@types"` if you want the compiler to look inside it. > Does the "automatic" inclusion of @types https://github.com/types work by > looking...

here is the updated link: https://github.com/DefinitelyTyped/DefinitelyTyped/blob/bf35326342777b2f01644555646fb213db096aa7/types/abs/tsconfig.json