Twitter | Search | |
Chrome DevTools
Official account. Follow for latest news, features, tips, handy extensions and more.
2,447
Tweets
65
Following
73,902
Followers
Tweets
Chrome DevTools retweeted
Benedikt Meurer Jan 31
👋 Come and work with us on ! We're specifically looking for frontend engineers with a passion for building developer tooling. 👩‍🔧
Reply Retweet Like
Chrome DevTools retweeted
Addy Osmani Jan 28
Tip: has a Shadow Editor built in!
Reply Retweet Like
Chrome DevTools retweeted
Umar Hansa Jan 17
It's out! Making images lazy load with Chrome DevTools - I'm planning to make more videos in the next few weeks, what would you like to see?
Reply Retweet Like
Chrome DevTools retweeted
Mathias Bynens Jan 28
Puppeteer v2.1.0 is out! 🔥 ➡️ Chromium 80 ➡️ puppeteer.launch({product: 'firefox'}) Puppeteer can now talk to a real, unpatched Firefox binary. You no longer need to install puppeteer-firefox separately!
Reply Retweet Like
Chrome DevTools Jan 28
In collaboration with Mozilla, we’re proud to announce Puppeteer v2.1.0! 🔥 The new version works with Chromium 80 and now supports official Firefox binaries as well.
Reply Retweet Like
Chrome DevTools retweeted
Tim van der Lippe Jan 23
We are migrating to and found some blockers. Very pleased to see quick resolution and fixes in the TypeScript compiler, making future JS -> TS easier! Hopefully we can provide guidance when we are finished, for others who want to do the same.
Reply Retweet Like
Chrome DevTools Dec 13
Chrome DevTools is based on web technologies - it's a web app! You can make changes to make your own flavor of DevTools, without building the rest of Chrome
Reply Retweet Like
Chrome DevTools Dec 12
Coming up in Chrome 79
Reply Retweet Like
Chrome DevTools Dec 5
Chrome DevTools is getting better at debugging WebAssembly! By using DWARF debugging metadata, we now support: ➡️ native source mapping ➡️ debug breakpoints ➡️ useful stack traces This is just a first step towards a good Wasm debugging experience.
Reply Retweet Like
Chrome DevTools Dec 4
What’s new in DevTools in Chrome 80? ↳ let and class redeclarations in Console ↳ improvements to WebAssembly debugging, code coverage, Audit & Network panels
Reply Retweet Like
Chrome DevTools retweeted
AgentConf Dec 2
Meet Simon , one of Googles rising Stars. Simon is part of and will be speaking about innovations in "Chrome Developer Tools" at Be Quick to register and learn about future of using Chrome
Reply Retweet Like
Chrome DevTools retweeted
Chrome Developers Dec 3
The WebAssembly Summit 2020 now has a website, where you can apply for tickets, find our Code of Conduct and can keep up with future updates for the event! 👉 Remember: Application deadline is December 9th, 2019!
Reply Retweet Like
Chrome DevTools Nov 30
Replying to @mmems
It been there for quite some time.
Reply Retweet Like
Chrome DevTools Nov 29
Ever wondered how to break on Array.prototype.sort, but only if every element in the array is a hiragana character?
Reply Retweet Like
Chrome DevTools retweeted
Yang Guo Nov 28
Pro-tip: if the function is still on the stack, select the stack frame to see the stack locals.
Reply Retweet Like
Chrome DevTools Nov 29
Replying to @_ColinTao @v8js
Record a performance trace in the Performance panel during page load, and look for compilation tasks in the ThreadPoolForegroundWorker timeline.
Reply Retweet Like
Chrome DevTools retweeted
Tomek Sułkowski Nov 29
Last year before December I've realized I have so many tips on I could share new ones every day for a month, so I put together an Advent Calendar on just this topic () This year I want to continue the tradition, with some adjustments: [1/3]
Reply Retweet Like
Chrome DevTools Nov 29
Replying to @andychiare
There has been some changes to the Performance panel, but much of this article is still very relevant:
Reply Retweet Like
Chrome DevTools Nov 21
Did you try this yet? Enable the experiment called "Record coverage while performance tracing".
Reply Retweet Like
Chrome DevTools Nov 20
Emulate `prefers-color-scheme: dark` from DevTools either from the Rendering drawer, or from the Command Menu (Ctrl/Cmd + Shift + P)
Reply Retweet Like