profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/paulirish/events. GitMemory does not store any data, but only uses NGINX to cache data for a period of time. The idea behind GitMemory is simply to give users a better reading experience.
Paul Irish paulirish Google Chrome, ♥z Palo Alto https://paul.irish/

GoogleChrome/lighthouse 23408

Automated auditing, performance metrics, and best practices for the web.

aFarkas/html5shiv 9845

This script is the defacto way to enable use of HTML5 sectioning elements in legacy Internet Explorer.

google/ios-webkit-debug-proxy 5345

A DevTools proxy (Chrome Remote Debugging Protocol) for iOS devices (Safari Remote Web Inspector).

ChromeDevTools/awesome-chrome-devtools 4766

Awesome tooling and resources in the Chrome DevTools & DevTools Protocol ecosystem

GoogleChrome/lighthouse-ci 4656

Automate running Lighthouse for every commit, viewing the changes, and preventing regressions

csnover/TraceKit 954

Attempts to create stack traces for unhandled JavaScript exceptions in all major browsers.

GoogleChrome/chrome-launcher 834

Launch Google Chrome with ease from node.

borismus/device.js 766

Semantic client-side device detection with Media Queries

GoogleChrome/devtools-docs 636

The legacy documentation for Chrome DevTools.

benschwarz/metaquery 328

A declarative responsive web design syntax. Breakpoints, defined in `<meta>`

push eventChromeDevTools/devtools-protocol

devtools-bot

commit sha 2258a64440dee65f9e5329e30d7ea6db51c9cb28

Updates

view details

push time in 4 hours

push eventChromeDevTools/devtools-protocol

devtools-bot

commit sha 98979600005f264dfe6862eda297f98b9ecb7f34

Updates

view details

push time in 11 hours

push eventChromeDevTools/devtools-protocol

Paul Irish

commit sha f62186c3fff55f17c892987cbbd8eb9f6f7d08b4

externs are dead as of Nov 2020. crbug.com/1011811#c1229

view details

push time in 17 hours

push eventChromeDevTools/devtools-protocol

Paul Irish

commit sha 72b31328d4eb48e7b9af9699b8aa33e2d1b276b3

chromium: use main rather than master

view details

push time in 18 hours

push eventpaulirish/npm-publish-devtools-frontend

Paul Irish

commit sha ea757577fb8e107a44a6aa03326d35a1a6a6bc81

use main instead of master

view details

push time in 18 hours

create barnchpaulirish/source-map-js

branch : patch-0.6.1

created branch time in 19 hours

push eventpaulirish/source-map-js

Paul Irish

commit sha 103073c3c38c61d07de2e5cd66fd396b552f2e95

stats to string

view details

push time in 19 hours

created tagpaulirish/source-map-js

tagv0.6.2

fork of 7rulnik/source-map-js (which is ultimately a fork of mozilla/sourcemap@0.6.1 (pre-wasm))

created time in 19 hours

create barnchpaulirish/source-map-js

branch : cdt

created branch time in 19 hours

created repositorypaulirish/source-map-js

fork of 7rulnik/source-map-js (which is ultimately a fork of mozilla/sourcemap@0.6.1 (pre-wasm))

created time in 19 hours

Pull request review commentgoogleads/publisher-ads-lighthouse-plugin

updates for type changes in lighthouse 8.4

  *  * The export list can be semi-auto generated by running the following command:  *- *   find node_modules/lighthouse/types/**.d.ts | sed -E "s#node_modules/(.*).d.ts#import '\1';#g"+ *   find node_modules/lighthouse/types node_modules/lighthouse/types/lhr -name '*.d.ts' -maxdepth 1 | sed -E "s#node_modules/(.*).d.ts#import '\1';#g"

not wildly better but the find bit can be abbreviated a tad with bracket expansion (works in all shells)

find node_modules/lighthouse/types{,/lhr} -name '*.d.ts' -maxdepth 1

weird syntax, especially for directory paths, but .. it works.

brendankenny

comment created time in a day

PullRequestReviewEvent

push eventChromeDevTools/devtools-protocol

devtools-bot

commit sha e00385c9e9f9453623267b72723db578c35ad4bc

Updates

view details

push time in 4 days

issue commentGoogleChrome/lighthouse

RFC: Allow passing in of a existing page debugger URL to lighthouse

@praveenralla you want to do #1769 but using the JS API and with puppeteer. This is enabled by #11313 which is currently under development.

we don't have documentation for it (and its not formally launched). if you want to try things out yourself, you can look at https://github.com/GoogleChrome/lighthouse/blob/6b95928efa51dd9b122df0d77ddfef95aeeea13f/lighthouse-core/test/fraggle-rock/api-test-pptr.js#L115-L118 and piece it together.

joelgriffith

comment created time in 5 days

PR opened PlanScore/FrontPage

remove unneeded highcharts data module

fixes https://github.com/PlanScore/PlanScore/issues/405 - the Cannot read property 'doc' of undefined error

afaict, this module isn't needed. I blocked the request and the map on the homepage works just fine.

I tracked back to where it was added... and I also don't see any csv/table/googlespreadsheets references there, so i'm not sure why it was ever added: https://github.com/PlanScore/FrontPage/commit/e3ca9343dbd2395ed274b65ff707b7b8cc601a24#diff-b769209f263118a83776e8b4e6610d58bc16f35ec8de0062e6d5c20352b3ea74R16

+0 -1

0 comment

1 changed file

pr created time in 5 days

create barnchPlanScore/FrontPage

branch : paulirish-patch-1

created branch time in 5 days

Pull request review commentGoogleChrome/lighthouse

report: inject report/assets/styles.css via components.js

 function createSnippetLineComponent(dom) {   return el0; } +/**+ * @param {DOM} dom+ */+function createStylesComponent(dom) {

multiple injections of these global styles doesnt cause any problems.. so i think we should just roll with it for now .

connorjclark

comment created time in 5 days

PullRequestReviewEvent

push eventdiveintomark/opensourceampersands.org

Paul Irish

commit sha 86d86a7676355f5392475da90e918b8661e34764

fix simplebits link. kernest link is now deadzo, but amazingly the peter-wiegel.de link is STILL GOOD. AND UPDATED!

view details

push time in 6 days

push eventChromeDevTools/devtools-protocol

devtools-bot

commit sha 7467d68b58999baea0dec4e78ea9c899fbe28bd5

Updates

view details

push time in 6 days

PullRequestReviewEvent
PullRequestReviewEvent

Pull request review commentGoogleChrome/lighthouse

report: sort audits by weight

 export class Util {           });         }       });++      category.auditRefs.sort((a, b) => {

(aside from my above comments.. i think this definitely improves the accessibility category) 👍

connorjclark

comment created time in 6 days

PullRequestReviewEvent

Pull request review commentGoogleChrome/lighthouse

report: sort audits by weight

 export class Util {           });         }       });++      category.auditRefs.sort((a, b) => {

this might be a better fit in the category renderer since we're really using it for rendering side effects.

i dont care too much about placement.. this location also seems fine. but i do think we should skip performance category entirely. (really only to avoid moving the metrics... but we know the rest of the category is all 0 weight)

connorjclark

comment created time in 6 days

PullRequestReviewEvent

Pull request review commentGoogleChrome/lighthouse

report: sort audits by weight

 export class Util {           });         }       });++      category.auditRefs.sort((a, b) => {

I think it may have been more like early -> mid -> late load metrics? @paulirish

yup. that's been the logic to the metric order.

also FCP/SI/TTI have been in the same location since v5 (and perhaps even earlier).

at least in the metric case, we have a link about how it works plus the calculator, so i dont feel bad if we dont have the metrics sorted by weight.

connorjclark

comment created time in 6 days

PullRequestReviewEvent

push eventGoogleChrome/lighthouse

Connor Clark

commit sha fa69d24bcdbcdfaa0a82dc31178f96001f313adf

misc(proto): add i18n.icuMessagePaths (#13068)

view details

push time in 6 days

delete branch GoogleChrome/lighthouse

delete branch : messagepaths-proto

delete time in 6 days