I will never forget how Apple tries to gaslight me into thinking I spelled "forbidden" wrong.

This time on Zed suggestions: aside from once again messed up weight, the first suggested action is *destructive*. The second one is the one I want. The fact that the third is even on this list is insane. Why are you like this, Zed? 😔

I tried this really good tea recently and it's nice.

The best job is that done with care, but if you're in a medical field, this is a must in my books. I've seen way too many doctors whose biggest contribution to society would be quitting.

If you are a security company, there's no better time than now to reap publicity points by sending open source maintainers free Yubikeys. GitHub should be doing this, honestly, once your repo reaches a certain scale.

I have successfully written the most flexible DOCX -> AST parser out there. For my needs.

💡 Did you know that Playwright has built-in visual regression testing? You can assert on entire pages or individual locators with the same ".toHaveScreenshot()" matcher.

You might even say this value is extremely unknown.

📣 React E2E Testing with Playwright is 40% OFF until next Thursday 📣 Dive into 13 hands-on exercises to learn how to: - Efficiently configure Playwright; - Test authentication, from basic to 2FA and passkeys; - Write tests by recording your browser sessions. And more! 👇

💡 The most important part of any test is the assertions. And in E2E tests those can get quite complex sometimes. But did you know theres "expect().toPass()" in Playwright just for that?

What have I ever done to you, GitHub, to squeeze me so?

There's been a lot of work on fixing memory leaks across MSW libraries in the past months. I love that! Even more than that, I love that we now have a few memory snapshot tests to prevent those leaks from happening. Beautiful.

💡 Suspect a flaky test? A flaky test suite? Use the "--repeat-each" flag in Playwright CLI to repeat each test case the given number of times. I used to have a custom bash script for this. It's so nice it comes built-in into the testing framework!

A few months ago, I went to give a talk for a local meetup. It was hosted in the same space where I went to listen to my first tech talk about 8 years ago. Coming back as a speaker was rather heartwarming. Chase the uncomfortable, folks. Keep growing.

Happy Saturday! Here's a sheep pen. You're welcome.

When was the last time Volume Control on your OS was entertaining? Exactly. How much we've lost.

I'm excited to announce "React End-to-end Testing with Playwright"! 🎉 Complete your testing journey by learning how to use Playwright to test your entire app. I'm talking full browser automation, user journeys, auth, search, test setup, debugging tips... Here's what's inside 👇

MSW has doubled in weekly downloads in the past 5 months 🤯 It's not just the most used API mocking library, it's one of the most used libraries in JavaScript in general. I attribute this to ShadCN adopting it. I also attribute it to every developer who advocated for it. Thanks!

📦 [email protected] introduces a new API called "finalize" for scheduling cleanups after the request handler is finished. This is your go-to choice for managing side effect cleanup in your mocks.

Web standards make it extremely easy to create agnostic tooling that runs everywhere. Third-party frameworks and libraries egregiously pulling the blanket by monkey patching and re-inventing those APIs makes it harder than ever.

The Axios npm compromise was a social engineering attack — not a leaked password, not a stolen key. The attacker hijacked the maintainer's *live browser session*. As far as npm was concerned, they *were* the maintainer. This exposes a dangerous gap in how we think about supply chain security. 👇

@vitest.dev is going framework agnostic, and we need your feedback!

Final touches on this colossus. You know the material goes hard when creating a custom fixture for type-safe routing in tests is in the "Fundamentals". Well, it is fundamental! And you'll be building on top of that in no time. Stay tuned.

Pre orders are now live for Together is a Distant Star! Join me on my journey as I read all 12 stories then hit that pre order button! youtu.be/zO9t_Qj4DP4?...

I am extremely grateful to be working on the best automated testing resources on the web right now ❤️ Means a lot to me, knowing that every exercise, every advice, is going to save somebody a ton of time and make them fall in love with testing like I did.

Node.js 18.8.0 was 4 years ago. Node.js 20 is EOL as of today. It's painful that developers still have to waste their time trying Jest to run ESM.

✨ I just released a new (free!) tool for creating custom Bézier curves! courses.joshwcomeau.com/tools/bezier It has one special feature that I haven’t seen anywhere else, and it allows us to do something pretty cool. 🧵

The evolutionary downgrade from goldfish to silverfish is something I still think about every day.

It's undocumented, but I released an "onUpgrade" callback to handle connection upgrades from HTTP to WebSocket for matching handlers. This is only relevant for Node.js and custom environments.

I’m so excited to reveal the title for my short story in our Belonging anthology today! 😍 Coming May 19th! How far would you go to find where you belong? (Links in the comments!)

People comparing Mouse P.I. to Doom/Bioshock, have we played the same games?

If you have any kind of digital presence whatsoever, running a business, selling goods, please make it your top priority to have your website discoverable in under 2 clicks from anywhere you can be found. It's absurd how hard it is to find some indie folks on the web.

May I run an API idea through you? What do you think the `waitUntil` function does here?

I submitted an application for an OSS program in one startup company. They haven't reached out in 2 months but promptly added my email to the marketing list. I've never agreed for my data to be used that way. In fact, there's nothing about it in their policies. Yeah.

Do I have any friends using MSW in governmental institutions, banks, healthcare systems, critical infrastructure? Raise your hand, I'd like to learn more.

Zed just rolled out an update that completely breaks my workflow. It merges all windows, messing up window navigation hotkeys. It turns them into workspaces for AI or whatever. Please don't do that. If you disrupt my flow, you're speedrunning my hatred toward your features.

AI will not take your software engineering job from you. But an AI-suggested "DROP TABLE users" in production might.

Maybe I'm missing something, but these two are identical in every possible way, are they not? I invite you to a find the difference game. Go!

They couldn't have picked a better name for the last moon mission. Everybody's inspired by this stupendous achievement for the mankind, and Artem is too.

The amount of slop here is staggering.

This image makes me happy. I want more developers enjoying Vitest. You are missing out big time if you aren't using it in 2026.

So AI doesn't understand the internal MSW architecture (the worker source) at all. Not sure if I should be sad or proud.

My next workshop is 2h 10m of condensed problem solving and pure knowledge on end-to-end testing with Playwright. That's a whopping movie on the topic 😅

My favorite kind of articles is "Playwright vs Jest" or "React vs JavaScript". You can feel all the absurd amount of research behind them seeping through the title alone.

I built Data as the means to do data-first API mocking, but it turned out that all you need is schema seeding and ORM-like querying, which are general purpose. Could you give it a try? Experiment, try breaking it, that kind of stuff. Thanks! github.com/mswjs/data

Migrated to oxlint the other day and the experience is smooth so far! Oh, and insanely fast. Like did-it-run-at-all-huh kind of fast.

One more scene and the act 2 of my novel might be complete. I got all the details planned out, the only thing left to do is to sit down and write.

TIL MSW doesn't really support intercepting form submissions since we guard against "navigate" requests. Historically, that guard was put there to prevent you from accidentally mocking your index.html or main.js. I'm considering removing it and introducing proper form handling.

I might be stupid on this, but why aren't browsers sending the client's dimensions to the server so it can fine-tune the rendering strategy knowing where the fold is?

I'm slowly coming around to granular entrypoints being peak ergonomics.