Asynchronous iteration (for-await-of) and ForOfStatement deprecation

'use strict';

(async () => {
  for await (const item of [Promise.resolve('a'), Promise.resolve('b')]) {
    console.log(item);
  }
})();

  4:3  error  iterators/generators require regenerator-runtime, which is too heavyweight for this guide to allow them. Separately, loops should be avoided in favor of array iterations  no-restricted-syntax

Should the ForOfStatement entry in no-restricted-syntax be alleviated in such cases? Maybe it is worth to remove the second part of the message (“loops should be avoided in favor of array iterations”), since there seems to be no easy different way for array asynchronous iteration?

Is there a way for AST parser to distinguish an async ForOfStatement from a sync one?

[ljharb]

@vsemozhetbyt if you’re in a node-only environment, you can certainly override rules that are concerned with transpilation overhead.

[ljharb]

For learning how the language works, a style guide isn’t going to be super helpful. Use every part of the language to learn! A style guide helps you mitigate and avoid and minimize the bad parts, once you already know how they work.