Shout out to @eleventy's Fetch plugin.

Every time I've needed to do something I'd consider esoteric recently, it's had a clean solution – a perfect combo of simplicity on the surface to get started with and accessible low-level APIs.

Solid work @zachleat!

Another screenshot for my "we [as an industry] can do better" folder... scrolling down on a Forbes article consistently bricks the page.

*checks console* yup, it's *that* JS framework.

It's a fucking static article 🤦‍♂️

If you haven't already, grab @keithamus's polyfill [1], it's time to adopt the Invoker Commands API.

[1]: https://github.com/keithamus/invokers-polyfill/
https://toot.wales/@Lukew/114155382524259744

I get why the prevailing sentiment is most developers hate writing tests, but whenever I skip writing tests for something seemingly inocuous and non-mission-critical, I still invariably come to regret it, usually by my third "Bug fix stupid mistake" PR.

This goes double now we're in the era of AI autocomplete generating legit-looking slop.

And triple on any JavaScript/web project where the nuances of the language and browser mean that slow feedback loop *will* come back to bite you.