Cannot find typings with typescript@beta and @types

[SebastianStehle]

Hi,

I am testing the new beta version of ts 2.0. In Visual Studio Code everything looks fine, but when I run my webpack build I get a lot of erros like

"Cannot find name Promise"
"Cannot find name Require"

I have added the same typings than before using the @types/... npm modules.

[blakeembrey]

Have you tried debugging anything or running it with tsc? I know it's not looked up automatically, but there's a types property in tsconfig.json for that, so those errors make sense and probably are issues with tsc unless you've configured it. Please make sure this is a ts-loader issue and not a configuration issue by running tsc and providing a minimal reproduction.

[SebastianStehle]

Yeah, sure. When I run tsc standalone it works well (I get one error in angular2, but this is another problem ;))

[blakeembrey]

And is that a global version or a local version?

[SebastianStehle]

tsc? it is a global version, but the same version

[blakeembrey]

Can you provide a reproduction for someone to look over?

[SebastianStehle]

Sorry to waste your time. I was just too lazy to read the documentation carefully. I just have to add the typings to the types folder.

[seanchas116]

Hi, I reproduced this problem.

https://github.com/seanchas116/ts-loader-global-types

In this project, tsc just works but webpack (with ts-loader) fails with
Cannot find module 'path'. and Cannot find name 'process'.

[SebastianStehle]

I realized that I have to add the 3 typings packages to the types config: types: ['core-js', 'node', 'jasmine']

Dont know why it works with tsc, but it works fine now.

[seanchas116]

Specifying types: ['node'] in compilerOptions in tsconfig also fixed my project. (thanks @SebastianStehle !)

[gxsjtu]

i do not know why close the issue?
'can-use' and 'good-to-use' is different, it is redundant to declare types in tsconfig.json.

[blakeembrey]

@gxsjtu make a PR. There's duplicate issues for this which you have already commented on.