(beta.11-webpack) Promise - Corresponding file is not included in tsconfig.json

Please provide us with the following information:

OS? Windows 7, 8 or 10. Linux (which distribution). Mac OSX (Yosemite? El Capitan?) ubuntu 16.04
Versions. Please run ng --version. If there’s nothing outputted, please run in a Terminal: node --version and paste the result here:

Could not start watchman; falling back to NodeWatcher for file system events.
Visit http://ember-cli.com/user-guide/#watchman for more info.
angular-cli: 1.0.0-beta.11-webpack
node: 5.11.1
os: linux x64

Repro steps. Was this an app that wasn’t created using the CLI? What change did you do on your code? etc.

the app was build with angular-cli@beta-10. I followed upgrade instructions and Promises no longer worked, along with styles.

The log given by the failure. Normally this include a stack trace and some more information.

No errors client side. Just in webstorm.

Mention any other details that might be useful.

ran `npm i @types/es6-promise` and tried adding "es6-promise" to "types":["jasmine"] array and that didn't work. Makes my app unusable.

Thanks! We’ll be in touch soon.

UPDATE Promises still compile and work, but it shows all the errors in webstorm. Not sure if I should just suppress statements with Promise types and .then() statements or not.

Issue Analytics

State:
Created 7 years ago
Comments:24 (2 by maintainers)

Top GitHub Comments

34reactions

suaucommented, Oct 22, 2016

I had this problem in quite a few projects with IntelliJ. Here is how to get rid of it:

Install Typescript 2.X
Go to Preferences > Languages and Frameworks > Typescript.

set Typescript version custom, navigate to /usr/local/lib/node_modules/typescript/lib (if you use brew, it’s somewhere else)
check “Use Typescript Service (Experimental)”

you’ll have to do this for every project. Good news is, this should use Typescripts own service, meaning this should work for every Typescript version in the future. (Until someone breaks it of course)

9reactions

eshellcommented, Aug 3, 2016

After doing the same thing over again a few times I managed to get it to work.

npm i @types/es6-promise then added es6-promise to types in tsconfig.json

for some reason those steps didn’t work the first time, now it does.

Top Results From Across the Web

How to resolve "Corresponding file not included in tsconfig. ...

I can compile the code fine with tsc without errors and it's working as expected. What is PhpStorm's / WebStorm's problem? $ jq...

TSConfig Reference - Docs on every TSConfig option

This config file will include all packages under ./typings and ./vendor/types , and no packages from ./node_modules/@types . All paths are relative to...

48 answers on StackOverflow to the most popular Angular ...

We have to import OnInit in order to use like this (actually implementing OnInit is not mandatory but considered good practice):

Confusing error "Corresponding file is not included in ...

My tsconfig.json two levels down from the project root in a folder with all *.ts files. The option "Resolve objects using tsconfig.

Compiler Options

Option Type Default ‑‑allowJs boolean false ‑‑allowSyntheticDefaultImports boolean module === "system" or ‑‑esModuleInterop ‑‑allowUmdGlobalAccess boolean false