New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 612493 link

Starred by 2 users

Issue metadata

Status: Fixed
Owner:
Last visit 29 days ago
Closed: Dec 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Bug



Sign in to add a comment

Support async/await in devtools

Project Member Reported by littledan@chromium.org, May 17 2016

Issue description

The main issue I'm aware of is the lack of support for async/await in the various JavaScript parsers that devools uses. Some support is implemented, however:
- CodeMirror just got a commit for this: https://github.com/codemirror/CodeMirror/commit/b2c11167b61d20cbba14eaebde00a28f0a8e4bc5
- Acorn has a plugin to support async/await parsing https://github.com/MatAtBread/acorn-es7-plugin

In addition to these parsers, there needs to be integration testing done to ensure that stack traces and promise debugging features all work as expected in conjunction with async/await.

You can use async/await in Chrome in testing with --js-flags=--harmony-async-await .
 
Components: Platform>DevTools
Labels: -Pri-3 Hotlist-Polish Pri-1
Status: Started (was: Assigned)
Started: https://codereview.chromium.org/2569563002/
Thanks for following up on this. As a possible optional follow-on, DevTools could also allow await expressions at the top level, as suggested in https://bugs.webkit.org/show_bug.cgi?id=165681
Status: Fixed (was: Started)
Thanks, a filed a separate bug for that:  crbug.com/673441 

Comment 6 by kayce@google.com, Jan 28 2017

Labels: DevTools-Release-Notes-Feature

Sign in to add a comment