New to DevTools in Chrome 68:
- Eager Evaluation. As you type expressions, the Console previews the result.
- Argument hints. As you type functions, the Console shows you the expected arguments for that function.
- Function autocompletion. After typing a function call such as
document.querySelector('p'), the Console shows you the functions and properties that the return value supports.
- ES2017 keywords in the Console. Keywords such as
awaitare now available in the Console's autocomplete UI.
- Lighthouse 3.0 in the Audits panel. Faster, more consistent audits, a new UI, and new audits.
- Adding property paths to the Watch pane. Add properties from the Scope pane to the Watch pane.
- "Show timestamps" moved to Settings.
Read on, or watch the video version of the release notes, below.
Chrome 68 ships with a few new Console features related to autocompletion and previewing.
When you type an expression in the Console, the Console can now show a preview of the result of that expression below your cursor.
To enable Eager Evaluation:
- Open the Console.
- Open Console Settings .
- Enable the Eager evaluation checkbox.
DevTools does not eager evaluate if the expression causes side effects.
As you're typing out functions, the Console now shows you the arguments that the function expects.
- A question mark before an arg, such as
?options, represents an optional arg.
- An ellipsis before an arg, such as
...items, represents a spread.
- Some functions, such as
CSS.supports(), accept multiple argument signatures.
Autocomplete after function executions
After enabling Eager Evaluation, the Console now also shows you which properties and functions are available after you type out a function.
ES2017 keywords in autocomplete
ES2017 keywords, such as
await, are now available in the Console's autocomplete UI.
Faster, more reliable audits, a new UI, and new audits
Chrome 68 ships with Lighthouse 3.0. The next sections are a roundup of some of the biggest changes. See Announcing Lighthouse 3.0 for the full story.
Faster, more reliable audits
Lighthouse 3.0 has a new internal auditing engine, codenamed Lantern, which completes your audits faster, and with less variance between runs.
Lighthouse 3.0 also brings a new UI, thanks to a collaboration between the Lighthouse and Chrome UX (Research & Design) teams.
Lighthouse 3.0 also ships with 4 new audits:
- First Contentful Paint
- robots.txt is not valid
- Use video formats for animated content
- Avoid multiple, costly round trips to any origin
Chrome 68 supports a new numeric primitive called
BigInt lets you represent
integers with arbitrary precision. Try it out in the Console:
Add property path to watch
While paused on a breakpoint, right-click a property in the Scope pane and select Add property path to watch to add that property to the Watch pane.
"Show timestamps" moved to settings
The Show timestamps checkbox previously in Console Settings has moved to Settings.
Was this page helpful?
To discuss the new features and changes in this post, or anything else related to DevTools:
- File bug reports at Chromium Bugs.
- Discuss features and changes on the Mailing List. Please don't use the mailing list for support questions. Use Stack Overflow, instead.
- Get help on how to use DevTools on Stack Overflow. Please don't file bugs on Stack Overflow. Use Chromium Bugs, instead.
- Tweet us at @ChromeDevTools.
- File bugs on this doc in the Web Fundamentals repository.
If you're on Mac or Windows, please consider using Chrome Canary as your default development browser. If you report a bug or a change that you don't like while it's still in Canary, the DevTools team can address your feedback significantly faster.
Previous release notes
See the devtools-whatsnew tag for links to all previous DevTools release notes.