-
-
Notifications
You must be signed in to change notification settings - Fork 27k
Allow flag to disable transformation of async/await calls #2990
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Yea. I think there's an issue for allowing different environments for development and production. Could you look for it? |
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) |
Any progress towards this? cc @gaearon |
Nothing on this front yet, @NeekSandhu. Please keep an eye on #1249. |
I've been, that discussion has been been still for quite some time. |
You can try to push that pull request forward, but we won't be adding special treatment for |
Feel free to make a new PR. 😄 |
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
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 onon hitting step over I jump to, as I'd expect
... 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
The text was updated successfully, but these errors were encountered: