jjenzz.com

When building React apps, many of us have probably craved a context selector at some point.

Applications often end up with skeletons, spinners, shimmer effects, loading overlays, suspense fallbacks, and all sorts of other UI whose sole purpose is to occupy the space where data should eventually appear.

Okay, the title is a bit hooky, but the idea behind it is feeling more relevant than ever.

If you've used local-first libraries before, you'll know the pitch.

There’s been a lot of buzz around Web Components (WCs) lately, and honestly, I’ve felt the pain myself.

Over the years, I've tried many ways of getting data into my apps—XMLHttpRequest, fetch, Apollo GraphQL, React Query, Remix loaders, React Server Components and more.

There has been a lot of talk on the socials lately about progressive enhancement.

With all the best intentions, codebases frequently end up a tangled web of components, abstractions, and global state (managed by a third party library) making the smallest of changes a living nightmare, and maintenance a balancing act.

It’s tempting to always control the components we implement.

Breadcrumbs can be a useful tool to help users find their place within your website or application.

Compound components provide a declarative API that can allow for some impressive solutions to everyday problems.