Phase 1 of the secret project complete. So stocked about it. Some of the best code I've written in a while. Excited to continue once I have a moment.

Anyone knows how to assert on optional parameters in type testing (Vitest)? I constantly get parameter(n) inferred as never if it's an optional object.

Year 2025. Still no way to check if a value is an object in JavaScript unless you typeof x === 'object' && x != null *sighs* If anything, JS should contain checks for its _unorthodox_ types as a must.

A few updates are coming around MSW. Exciting!

Is there a way to force Playwright to always await idle network on any navigation? Without manual { waitUntil: 'networkidle' } everywhere?

Still hard to believe I've not seen a single major reviewer acknowledge that the new iphone's design is the first *hardware* rip-off Apple has ever done. People just... roll with it. I think I understand why so many buy a new phone every year now.

I think I've reached Playwright nirvana. - In-test test app definition; - Compiled and served by Vite; - `evaluate` wraps a JSHandle to act on values *on the client*. I've been dreaming about testing MSW this way for years. Tears of joy.

These days, I find myself in a dire need of using Vite to compile test cases for Playwright. And I want it all in the same test file. Has no one built this yet?

Pre-nerf pride.

This kind of pull requests hits differently.

I'm not going to tell you what a life-changing thing it is to have a controller with extra buttons on the back so you can remap them to jump/dash and perform acrobatics in Silksong independently from attacking. The way it's been intended.

Drizzle's "relationName" is the most elegant alternative to the "belongsTo" absurdity I've ever seen. Brilliantly done. I'd personally name it "role" instead, but this is entirely subjective. orm.drizzle.team/docs/relati...

Working on something exciting but I think I'ma pull a Team Cherry on this one. No news until it's completely done.

After apologizing profusely, the LLM admitted defeat.

Is this an invalid Zod schema? I'm getting "Maximum call stack size exceeded" when creating multiple users (i.e. calling ".validate()" on initial values). Can someone please confirm this is okay?

So it turns out even with AsyncContext in the browser, the `worker.boundary()` API wouldn't be possible. MSW listens to a request event from the worker, and event listeners aren't considered async context so you cannot grab the latest state from AsyncContext within them.

A shower thought: if the window and ServiceWorkerGlobalContext share Cache, does that technically mean I can put responses in cache on the client and affect the request resolution in the worker? Now this is fascinating.

Daily side quest: Prettier fails to resolve its plugins in symlink-based package stores. Not how I imagined spending my evening. Completed but at what cost. What cost.

Dealing with an interesting race condition in MSW. Imagine firing a request and then calling worker.stop(). You'd still expect that request to be mocked, but that's not easy for MSW to understand. Would love some help!

Imagine being Apple and publicly admitting your design defeat by copying Pixel. iPhone is dead. The 13 mini I own right now will be my last iPhone. And as any change, it's likely for the best.

The authors of the Service Worker API sure loved Promise chaining 😅 event.waitUntil and event.respondWith should've also supported a function that returns a Promise. Would make literally any operation much easier to write.

A 15-LOC service worker that only caches images can yield up to x6 times faster page load time. Service workers are pretty good and you should use them more btw.

Looks like I'm skipping MacOS updates for the next decade or so. What in the name of all that's holy is this?!

Foster new contributors. Don't expect them to get all right at once and do everything. Guide them. Advise them. Help them (commits are free btw).

Around 62k words and the Act I of the fantasy story is complete! Love the changes. Editing is brutal but every iteration makes the writing feel more like an actual book. A feeling worth chasing.

15.5h into Silksong, only +1 mask and 0 needle damage upgrades. This game is either ginormous or we're in for a hardcore ride with no damage scaling.

I am becoming increasingly convinced that calling `setupWorker()` multiple times on the same page is a huge anti-pattern. I should've made this more clear in the past. Thinking on the right way to approach this...

"You expect it to work but that's now how Service Workers work." I love this sentence.

We have to protect the devs who file immaculate reproduction repos with clear instructions at all cost. They are the absolute best.

History.

Happy Silksong day to those who celebrate!

📣 Last couple of HOURS to grab the newest workshop, Advanced Vitest Patterns, at a 20% discount! Dive deep, customize your experience, and improve your tests' performance. A must-have for any Vitest user. www.epicweb.dev/workshops/a...

Most of the articles I write are done in one sitting with a bit of preparation beforehand (outline + research). Unless it's a 5,000 word+ technical dive or an interactive demo, the piece has been written and edited in one go.

📰 Today, I write about the default behaviors that I love in Vitest. If you are wondering why prefer Vitest over other test runners, here's a solid list of answers. Give it a read! www.epicweb.dev/incredible-...

💡 Did you know that you can teach your test runner compare things that are structurally different but equal semantically? Let's explore how 👇

@francoisbest.com hi! How did the yesterday's stream go? Sorry I couldn't join. Anything fun you hacked with MSW?

One more DAY remaining to get my latest workshop on Advanced Vitest Patterns at 20% off! 🤯 If you want to become a Vitest superuser, this one is for you. Learn how Vitest works, how to customize it and build custom experiences on top. www.epicweb.dev/workshops/a...

A few months ago, I shipped a tiny improvement to Vitest to help you annotate custom matchers. Now, you extend a single interface called `Matchers` and that gives you symmetric and asymmetric matchers as well as correctly annotates matcher declaration. Have you tried this yet?

@francoisbest.com hi! Now that Zod supports serialization/deserialization, is there any reason not to use it in Nuqs? (watching your video on @devtools.fm)

Netflix: we release all episodes all at once! Also Netflix: but we portion the flagship stuff so you stay subscribed longer. Just release episodes weekly. Boost the subscribers, bring back the cultural zeitgeist that shows used to have. Everybody wins.

Did you know that MSW is exactly 66.66% Service Workers?

Using sli.dev for my upcoming talk and loving it so far! Encountering tiny issues here and there but overall a solid library. Recommend.

Twitch turning the video stream off and switching to audio-only when you leave the tab for a bit is a really nice technique to save bandwidth. Smart!

You can use MSW (mswjs.io) to test backend APIs, btw. Controlling the network isn't exclusive to frontend! You're missing out.

You all questioned me when I closed up MSW's docs to LLMs, but now I (and anyone) can tell an AI-written article about it from a mile away (because it features the API that's been long deprecated). If you want to learn the tool, put in some work.

Imagine custom predicate functions and Server-Sent Events support landing in MSW within the same month.

I want as many developers as possible to experience the joy of refactoring their code when they have a good test suite by their side. It's infectious. You'd want that feeling all the time.

I am absolutely blessed to have incredible engineering friends. They support me. They challenge me. They inspire me. They give me a chance. They go out of the way to help me when they, frankly, have no reason to. I love you all. Hugs.

Weapons was not a good movie 😔

Imagine the world where successful new ideas do not get milked into oblivion with needless sequels but instead pave way to even more successful new ideas. Just imagine.