Allow flag to disable transformation of async/await calls

Now that Chrome devtools debugger supports stepping over async/await calls, it is extremely helpful when debugging async code.

For example, right now, if I’m paused on

40| const res = await fetch('https://example.com');
// sourcemapped code, not actual

and I hit step over, debugger suddenly jumps to some random line, totally out of context as far as I am concerned.

Now here’s where pure gold is, if await calls are not transformed by babel and remain as they are, and again I’m on

40| const res = await fetch('https://example.com');

on hitting step over I jump to, as I’d expect

41| const text = await res.text();

… and so on

Without this, the only option I can use is console.log, …really painful.

It would be a great addition, maybe we can have this behind a flag of some sort, like yarn start --keep-async

Thoughts, welcome

[zikaari]

The most relevant one I guess is this Make target browsers configurable #1249

(Underlying logic of both proposals is exact same, both involves skipping or applying polyfills/transformations)

[Timer]

Feel free to make a new PR. 😄