This is mostly for me to remember.
I needed to build a mapping of DevRel support to Blink Components, and I really didn’t want to have to manually work out all the components by hand.
If you want to get a list of components in Blink, there is a file that has all the details you need.
If you are Promise inclined, here is a quick way to do it.
fetch('https://storage.googleapis.com/chromium-owners/component_map.json') .then(body => body.json()) .then(d=>console.log(Object.keys(d["component-to-team"]).filter(i=>i.startsWith('Bli')).join(','))) .catch(console.err)
If you are async/await inclined, here is the same code.
let res = await fetch('https://storage.googleapis.com/chromium-owners/component_map.json'); let body = await res.json(); console.log(Object.keys(body["component-to-team"]).filter(i=>i.startsWith('Bli')).join(','))
Now to work out how we get a list of all the OWNERS programatically so that our team will always know the correct people to speak to.
I lead the Chrome Developer Relations team at Google.
We want people to have the best experience possible on the web without having to install a native app or produce content in a walled garden.
Our team tries to make it easier for developers to build on the web by supporting every Chrome release, creating great content to support developers on web.dev, contributing to MDN, helping to improve browser compatibility, and some of the best developer tools like Lighthouse, Workbox, Squoosh to name just a few.