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.
Posts by Artem Zakharchenko
Kind of crazy to think how much the craft has evolved since that time. I dare say JavaScript is a proper programming language now.
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 ๐
So does all software, really! It's always down to cost vs gain. I quite like working with Solid. The mental model shift is rather steep, but you can abandon hooks from day one.
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 never got over the fact how much API churn React is putting on me solely due to how it's designed.
Helps a ton trying other frameworks. It's such a bliss to never have to think about hooks again โค๏ธ
Sometimes the content just deserves a half like.
Thanks! Your contributions are making it better for everyone.
Yeah, I've taken a huge inspiration from Factorybot and Laravel's built-in ORM, as well as Drizzle and Prisma.
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
I haven't!
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.
You can cup one into another and put them on a mirror to achieve the said 'hands on his hands' effect.
The ringtone is #1 anxiety inducer for me ๐ฌ
That is clearly not the case as we see more and more frameworks working on server-side data fetching prioritization and out-of-order streaming to focus on critical parts of the UI.
Resizing is fine. For caching, there's the Vary header, but that depends what cache you mean.
Still shocked so many people got it.
It's not really about styling though. Knowing the client's fold means I can prioritize rendering the UI that's above it. Think data fetching, streaming, that stuff.
Elaborate.
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.
Oh right. Well. Yeah.
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?
The browser will not USE that code, but it has to import it to know it's unused. But even that aside, granular entrypoints create tiny universes within the library, helping with logic collocation and granular updates.
I want to embrace the ESM future wholeheartedly. And in the browser, importing "msw" will pull in EVERYTHING over the network, creating an absurdly large request waterfall of dependencies. Browser does no treeshaking. You importing just `http` will import graphgql, ws, etc.
I'm slowly coming around to granular entrypoints being peak ergonomics.
Specification-first API design is beneficial in so many ways, including being much easier to mock/test, too.
My take on API mock generators is that the only source of truth worth generating mocks from is your API specification. Anything else is a brittle abstraction whose appeal evaporates in no time in practice.
If you want to go this route, please invest into designing a spec.
Lana Dev Rel.
I have M2 Air. It fares with development surprisingly well, but I'm using it for personal things.