async/await compiles to yield outside of a generator

[ryasmi]

The following TypeScript with async/await...

public async get(from: number, to: number): Promise<Array<M>> {
  let models: Array<M> = await this.persistant_repo.get(from, to);

produces the following JavaScript with a yield outside of a generator...

ModelsRepoDecorator.prototype.get = function (from, to) {
  var _this = this;
  var models = yield this.persistant_repo.get(from, to);

I'm not certain, but I don't think yield should work outside of a generator. I'm running tsc src/**/*.ts --outDir dist --sourceMap and my tsconfig looks like this...

{
  "compilerOptions": {
    "module": "commonjs",
    "target": "ES6",
    "noImplicitAny": true,
    "removeComments": true,
    "preserveConstEnums": true,
    "sourceMap": true,
    "jsx": "react"
  }
}

I think this may be a duplicate of #4135, but I'm not sure how the solution there can be applied here.

[DanielRosenwasser]

I'm not seeing this behavior. Can you try out the current nightly by running npm install -g typescript@next and letting us know if that fixes it?

[ryasmi]

I have new errors on the nightly build, will look into this after Christmas @DanielRosenwasser, merry Christmas! 😄

[ryasmi]

@DanielRosenwasser the compiler seems to be ignoring my tsconfig.json file.

[DanielRosenwasser]

Can you share a minimal repro? Or share the project itself?

[ryasmi]

Nothing has changed in my project, on the nightly build you can use my tsconfig with a typescript file using a promise, run the command I shared above and you'll hit error TS2304: Cannot find name 'Promise' and if you use a async function you'll get error TS1311: Async functions are only available when targeting ECMAScript 6 and higher. I didn't get those errors previously.

[ryasmi]

Ok fixed those errors by just stuffing all of my options into a command (#5980 can't come soon enough).

find src -name "*.ts" -type f >ts-files.txt; tsc @ts-files.txt --module commonjs -t es6 --noImplicitAny --removeComments --preserveConstEnums --sourceMap --jsx react --outDir es6; rm -f ts-files.txt;

Now I get module errors like...

error TS2307: Cannot find module ...

Judging by some of the type errors I'm getting in addition to this, it's also ignoring my typings directory 😢 Sublime Text isn't showing any of these errors with the TypeScript package.

[ryasmi]

Everything compiles fine, but when I run tsc with the tsconfig below, I get TS2307 and TS2304 errors like it's ignoring the "node_modules" and "typings" directories. For the record, my project has three directories, "node_modules", "typings", and "src" (which contains my ts files). I'm running tsc from the root.

{
  "compilerOptions": {
    "module": "commonjs",
    "target": "es6",
    "noImplicitAny": true,
    "removeComments": true,
    "preserveConstEnums": true,
    "sourceMap": true,
    "jsx": "react",
    "outDir": "es6",
    "rootDir": "src"
  },
  "exclude": [
    "node_modules",
    "typings"
  ]
}

error TS2307: Cannot find module 'firebase'.
error TS2304: Cannot find name 'process'.

[DanielRosenwasser]

Without knowing more about your actual project, it's difficult for me to diagnose the issue. Can you share the repo at all?

[ryasmi]

Yeah sorry, I understand that, I can't share the repo though unfortunately. My original issue is resolved in the nightly so I'm happy to close this issue, however I think there are some issues in the nightly around node_modules and typings. If I manage to figure out exactly why I'll create a new issue. Thanks for trying to help @DanielRosenwasser.

[ryasmi]

For the record I've isolated my TS2307 issue in https://github.com/ryansmith94/TS2307-Issue @DanielRosenwasser

I have import * as React from 'react'; which is giving me the error Cannot find module 'react' in "./src/app.ts". However, react is installed in "./node_modules". My target and module compiler options are set to "es6". The error is given by the TypeScript Sublime Text 3 package (v0.11.1) and gulp-typescript (v2.10.0) with TypeScript (v1.7.5) installed globally via npm.

Quoted from a message I put on Gitter.

[ryasmi]

That issue has been resolved on Gitter.

[DanielRosenwasser]

In the interest of helping people who run into any similar issue, here is the link to the resolution in the Gitter chat on December 29, 2015 5:29 PM.