Semicolons issue

[taoeffect]

I've some code:

it('Should create user George', async function () {
  (await n.goto(page('new-user')))
  .should.containEql({code: 200, url: page('new-user')})
  // for some reason we have to access `this`
  // only *after* we call `await` once.
  this.timeout(12000)
  console.log(`<--${new Date().toTimeString()}-->`)
  console.log('typeof this:', typeof this, Object.keys(this))
  await n.wait(2000)
  console.log(`</-${new Date().toTimeString()}-->`)
  return n.wait('#response')
  .insert('input[name="name"]', 'George')
  .insert('input[name="email"]', 'george@lasvegas.com')
  .insert('input[name="password"]', '$$111$$')
  .click('form.new-user button.sign-in')
  .wait(() => document.querySelector('#response').innerText !== '')
  .evaluate(() => document.querySelector('#response').className)
  .should.finally.not.equal('error')
})

This results in an error if the this.timeout(12000) is the first line in the test because of an "ASI" (automatic semicolon insertion) issue.

Oddly enough, moving it up to the first line and putting a semicolon there as shown below works and passes the linter:

    it('Should create user George', async function () {
      // this semi-colon at the end of of this.timeout is *required*.
      // For details, see: https://phabricator.babeljs.io/T7372#78495
      this.timeout(12000);

I don't know why it passes the linter, but I am happy it does because otherwise I would have had to give up on standard.

Perhaps this quirk could be highlighted in the documentation? Seems like something that could drive many JS developers mad, especially now that async/await usage is becoming... wait for it... standard.

[taoeffect]

Oops, this was totally my fault. I had added /* eslint-disable no-spaced-func, no-unexpected-multiline */ to the top of the file because I did not want to have create variables. But I should have instead followed the advice in RULES.md (which I'd forgotten) and simply done ;(await ... instead.