Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

WebStorm, An async function or method in ES5/ES3 requires the 'Promise' constructor

I try to write tests in typescript (ES6) using WebStorm IDE. E.g.:

// Imports...

describe('Message', () => {
    const server = express();
    server.use(bodyParser.json());

    const messageService = { findAll: () => ['test'] };

    beforeAll(async () => {
        const module = await Test.createTestingModule({
            modules: [MessageModule],
        })...
    });

    // Tests...
});

However WebStorm IDE shows following error at async () =>

TS2705: An async function or method in ES5/ES3 requires the Promise constructor. Make sure you have a declaration for the Promise constructor or include ES2015 in your --lib option.

My tsconfig.json:

{
  "compilerOptions": {
    "module": "commonjs",
    "declaration": false,
    "noImplicitAny": false,
    "removeComments": true,
    "noLib": false,
    "emitDecoratorMetadata": true,
    "experimentalDecorators": true,
    "target": "es6",
    "sourceMap": true,
    "allowJs": true,
    "outDir": "./dist"
  },
  "include": [
    "src/**/*"
  ],
  "exclude": [
    "node_modules",
    "**/*.spec.ts"
  ]
}

I read ts An async function or method in ES5/ES3 requires the 'Promise' constructor and tried adding

"lib": [ "es2015" ]

however it does not have any effect. Any ideas what's wrong?

like image 498
UpCat Avatar asked Oct 20 '17 12:10

UpCat


2 Answers

Solution without editing the project sources

I had this problem with IntelliJ and resolved by changing my IDE settings:

Settings -> Language & Frameworks -> TypeScript

then in the "Options" field add:

--lib es2015

enter image description here

like image 199
Francesco Borzi Avatar answered Nov 01 '22 16:11

Francesco Borzi


Adding

"lib": [ "es2015" ]

to tsconfig.json should fix the issue. However it seems that your spec files are not included in your tsconfig.json (check "include":[] and "exclude":[] values). So the Typescript service must be using a different tsconfig.json for your files (may be a default one, if no tsconfig.json files that include your specs can be found) To fix the issue, make sure to specify the lib property in config that is used for your spec files processing

like image 30
lena Avatar answered Nov 01 '22 14:11

lena