DevTools in 2016: Accelerate your workflow - Google I/O 2016

What's the ideal web developer’s workflow? The Chrome DevTools team has asked this question over and over, only to realize that there isn't just one! So rather than bringing you to the DevTools, we're bringing the DevTools to you, wherever you are.
Learn how far our upcoming integration with your favorite editors goes, our new supercharged console with ES6, the new command palette and much much more.
Watch more Chrome talks at I/O 2016 here: goo.gl/JoMLpB
See all the talks from Google I/O 2016 here: goo.gl/olw6kV
Subscribe to the Chrome Developers channel at goo.gl/LLLNvf
#io16 #GoogleIO #GoogleIO2016

[@huseyngadirov7658]

Paul's speeches are always brilliant

[@ling6701]

That's pretty cool. Animation part is killing it. I love cmd shift P too.

[@riendlyf]

Your work makes my life much easier, --inspect is very cool, a necessary thing !!! Great upgrades

[@mr.camroe]

Awesome to see the support for debugging in Node! node-inspector was definitely a rough choice.. hope the PR gets merged!

[@MadhuraDarshana]

Super, i checked animation tab on my chrome dev tools, but seems like its still not there (tried updating to the latest) though.

[@tkhemani]

How do I get my hands on the private node build used here?

[@KimHogeling]

42:50 debug node with dev tools! Super powers 💪

[@NicholasIrvingAU]

Any ideas where weather-wonder-bb can be downloaded from?

[@natehill1370]

Very exciting news - especially the prospect of switching more easily between Chrome and Node debugging contexts. Unrelated yet important question - does anyone know what kind of glasses Paul Bakaus is wearing?

[@ronnienyaga]

Very neat. Hoping node accepts the PR.

[@browsermage]

very nice

[@Buddharey]

node -inspect should log the new url and open it automatically

[@JacquesvanWyk]

where can i learn how to set up gulp as they did, where as they save on chrome it updates?I am new to gulp.

[@OlivierTravers]

You can use a watch task, but that can be flaky if you use mounted volumes in Vagrant or Docker. I like BrowserSync, it can watch changes more reliably under the files: section of its Gulp task. It will even inject CSS changes without a full page refresh.

[@GoadvanzBluetooth]

DevTools. Interesting!

[@GitanesB]

Where can I get the "node2 --inspect" repo that he is using ???

[@VinayAggarwal]

github.com/nodejs/node/pull/6792

[@edwardspencer8982]

Are the CSS change highlighting changes still not in?

[@FrancisBoudreau]

You have to activate the experiments flags in chrome://flags, and after that the CSS changes highlight will show.

[@itsalivevideo]

Anyone know what terminal font that is?

[@itsalivevideo]

Turns out it's Operator Mono - $200. #firstworldfont :D

[@NikosKatsikanis]

much more friendly than webstorm's debugger

[@anonimo0486]

visual studio code!!! 😀😊

[@StingSting844]

19:26 - what kinda shell is that??

[@StingSting844]

+Andrew Vijay just found out that its the fishshell

[@NicholasIrvingAU]

+Andrew Vijay installed and liking it

[@StingSting844]

Marko Djordjevic its fishshell and its awesome

[@NavdeepGaur]

and I am the right hand man of Mr. Bond's arch enemy.

[@mika2666]

how many pauls does google have on the chrome/web devrel team XD

[@green10701]

Node.j debugger? Lol! 43:29 1. Console doesn't work. You can't type anything. 2. Files are not grouped in folders. Only a loooong list of all files. 3. It breaks every single time you save a file! You can't debug with it. Node v6.11.5 Downvote