Redundant use of `await` on a return value.

[TheEnmanuel23]

What version of standard?
12.0.1
What operating system, Node.js, and npm version?
macOS sierra v10.12.5
node: v8.9.3
npm: 5.5.1
What did you expect to happen?
No error, I have test with jest

in the version 11.0.1 it is working well for me

What actually happened?
throws error in the tests with async await

[TheEnmanuel23]

the solution that I found is
it('/with empty array', async () => { await expect(tipState.saveInitialStates([])).rejects.toMatchObject({ message: /states parameter is empty/ }) })

adding {} in arrow function

[LinusU]

This is intentional, it's because

async () => await foobar()

is the same as

async () => { return await foobar() }

which then has a redundant await, since the following will produce the same result:

async () => { return foobar() }

If you did not intend to return the return value of expect in the it-callback, I suggest changing to async () => { await ... } as you did, as that will only settle with undefined 👍