Async Iterators don't work

[pranaygp]

🐛 Bug Report

Async Iterators or generators simply don't work with jest even thought they're natively supported in Node 10

To Reproduce

0. Install Node 10.x.x
1. cd to a test project where jest works
2. add async function* foo() {} to some file
3. run your project (with yarn start or node index.js etc.)
4. Notice that it works
5. Try running your test cases yarn test
6. Notice that jest complains about "unexpected token *"

Expected behavior

The test suite should run normally and not throw this error

Link to repl or repo (highly encouraged)

Seems like repl.it doesn't have node 10. Sorry :/

Issues without a reproduction link are likely to stall.

Run npx envinfo --preset jest

Paste the results here:

npx: installed 1 in 1.672s

  System:
    OS: macOS High Sierra 10.13.5
    CPU: x64 Intel(R) Core(TM) i7-4770HQ CPU @ 2.20GHz
  Binaries:
    Node: 10.3.0 - ~/.nvm/versions/node/v10.3.0/bin/node
    Yarn: 1.7.0 - ~/.yarn/bin/yarn
    npm: 6.1.0 - ~/.nvm/versions/node/v10.3.0/bin/npm

[ASHISH932]

@pranaygp tried testing async function on node 10.5.0 and it is working fine.
Here is one example to test generator function:

[nooga]

@ASHISH932 I'm dealing with the exact same case as @pranaygp described and it or no it doesn't make a difference. I get that unexpected token * no matter what.

[nooga]

I've been able to get this working by:

1. Creating the following .babelrc in my project.

{
    "plugins": ["syntax-async-generators"]
}

2. Installing babel-plugin-syntax-async-generators by

npm install babel-plugin-syntax-async-generators --save-dev

After that, I got expected behavior. Having said that, I think that if those async generators and async iteration are natively supported by node starting from 10.5.0 tools like jest should support them out of box as well.

[ASHISH932]

@nooga you should be using env preset of babel(babel-preset-env) as it's support latest javascript feature, whenever it's get official . Here is an article to set up your react environment.

[nooga]

@ASHISH932 Thanks, although I don't use babel in my project directly and it has absolutely nothing to do with react.

[ASHISH932]

@nooga that's up to you to decide architecture of your project but if you read documentation of jest they have mentioned to use env preset

[shaunc]

@ASHISH932, I am using node 10.5. Still getting the error after I added a .babelrc.js (below). How do you suggest using babel-preset-env?

module.exports = {
  presets: [
    [
      '@babel/preset-env',
      {
        targets: {
          node: 'current'
        }
      }
      }
    ]
  ]
}

EDIT

Possibly related to the fact that I am using ts-jest, which skips babel -- kulshekhar/ts-jest#471 (comment)

AFAIK this should work without babel if node accepts without babel.

[anru]

Node does support async generators starting from version 10.3.
So jest should work without any babel configuration on latest node.

@shaunc if you are using babel this comment #4936 (comment) might be helpful for you

[SimenB]

This is essentially the same issue as #6829.

tl;dr: Jest uses babel by default, so you have to tell it to understand your syntax or explicitly disable babel.

You can follow babel/babel#7660 for what I think is the correct solution to this problem

[shaunc]

@SimenB in kulshekhar/ts-jest#471 the problem is that ts-jest passes typescript compiler results to jest without using babel by default. So

or explicitly disable babel.

doesn't actually work, but it should

[SimenB]

That's something that should be addressed in ts-jest then.

Remember that Babel is needed for code coverage, though.

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.