Follow Friday: if you’re into web components (in no particular order):

Nick Williams

Konnor Rogers

Burton Smith

Justin Fagnani

Michael Warren (he/him)

Every person on this list is worth clicking the button!

This day was going to come eventually, but here it is...

After 15 years, today is my last day at Google!

I'm incredibly proud of what I've accomplished at Google, and so fortunate to have worked with such awesome people on such interesting projects.

High Performance HTML Tables with Lit and CSS Contain

coryrylan.com/blog/high-perf…

Dynamic Contrast Layers with CSS Style Queries

coryrylan.com/blog/dynamic-c…

A developer shouldn't merely do what they're told.

Why? Because it's not a developer's job to merely follow orders.

We're paid to see the gaps.
We're paid to collaborate with others.
We're paid for our professional judgement.

So:
We should push back.
We should point out…

🌶️
Stop using process.env for frontend code, use package export conditions instead

Definitely make sure you watch the free stream on Wednesday - we have a lot of exciting announcements 🔥

One day this will be markup that works and I'm unreasonably excited about that.

ElementInternals.states is coming in Safari 17.4, which means only Firefox is left — and it's already available behind a flag.

It feels like browsers are moving faster these days!

caniuse.com/mdn-api_elemen…

I loved Blaze (Bazel) at Google... But your company will never, ever be able to do Bazel like Google does Blaze. And while it probably helps the build pipeline for your JVM-based whatever backend, it's an absolute hinderance for TypeScript/JavaScript development.

This is an exercise in defining component API. Every set of related options should be handled separately, with close attention to mutually exclusive options.

If you’re new to this as a designer, collab with Engineers, as you will want these to align in the end.

Proud to have implemented CSS CustomStateSet which is now shipping in Safari 17.4!

fun fact: its nearly impossible for engineers with 'view' access to see how a component is constructed in your library. This is extremely frustrating if your design systems team operates under a federated / contribution model.

#builtWithLit

Favorite plug n play library of the day github.com/google/wireit

In case you didn't know: There's work currently being done to add Observables to the web platform! There are even flags to play with it now in Chrome Canary.

You can follow along here: github.com/WICG/observable

If you are testing front-end code, my recommended setup today is to use Web Test Runner for unit tests and Playwright for e2e tests. You can configure Web Test Runner to use Playwright, and you can also configure Playwright to run tests against Storybook stories, providing a nice…

Honest

🔥New JS API just dropped in Webkit Nightly for checking if an element is visible or not.

It covers a bunch of HTML + CSS methods for hiding an element, including the upcoming CSS content-visibility API

Already in Firefox + Chrome.

Design systems are critical front-end infrastructure. They should prioritize quality over speed. But product teams often have ship at all costs, prioritizing speed over quality. I wrote a thing about how to square the difference:
bigmedium.com/ideas/design-s…