Okay, so I looked into the comments on the MSW usage in the latest State of JS, and the negative ones are either misunderstanding what mocking is or blatantly promoting what feels like their own tools. This made me happy. I don't consider any of that a relevant feedback.

I know there are a ton of people who think "mocks = bad". Not only is that a huge misconception, but if you truly abide by it, you will produce terrible tests. Mocking is a tool. Is a brush bad? Depends on who's holding it, I suppose. The same applies to mocking.

📦 MSW v2.12.8 fixes two issues that resulted in a memory leak in Node.js. Please update your projects! Release notes: github.com/mswjs/msw/r...

I will never be not amazed at how a seemingly trivial bugfix can suck you into a rabbit hole of issues that spans three dependencies deep. That was a fun quest!

Enjoyed talking about authentication in end-to-end tests in a recording today! The thing is, the way you approach authentication as a feature and as a prerequisite to test other features has one important difference. Overall, this is already my most detailed workshop to date ❤️

100M a week. Sheesh.

Can I pick your brain, folks? Reply with 3 topics you consider advanced in automated testing 👇

I genuinely don't know how npm cli and website aren't considered abandonware at this point. Trusted Publishing is broken, features behaving inconsistently across them, token management is non-existent, obscure error messages... 😔

Thank you, Santosh! ❤️

Can someone tell me what am I doing wrong? The whole point of trusted publishing is so I DON'T have to log in to npm to publish a package from a trusted workflow. So no tokens are involved.

One sponsor cancellation away from being unsustainable btw 😔

I am judging your framework based on how the principles you promote affect the testability of the end code. Good frameworks make your code easy to test. Bad frameworks riddle your code with side effects and dependencies, then check out and leave you in a mocking hell.

Once, my friend asked me if by teaching others I'm not creating competition for myself. I get where he was coming from, but that's not how I see it. We aren't in a race, we are in a life-long hackathon. If someone levels up, everyone wins. And I win, too.

🟦 #WORKSHOP DAY - Just Confirmed 😉 👨🏻‍💻 React Query - Beyond the Basics 👨🏻‍💻 with @tkdodo.eu Learn More & Save Your Seat NOW! ⚠️Limited Seats 👉🏼 react.paris

🟦 #WORKSHOP DAY - Just Confirmed 😉 👨🏻‍💻 Level Up Your URL State In Next.js With @nuqs.dev 👨🏻‍💻with @francoisbest.com Learn More & Save Your Seat NOW! ⚠️Limited Seats 👉🏼 react.paris

If you don't know how many emus there are in an inch, I don't think we can be friends.

Never in my life did I want to see a GUI when shortcutting to "Settings" in any editor. You literally have a tool for developers. Give me that JSON I can edit. Make the GUI gone. Why this matters is because editing a JSON is times faster and seeing that UI is disappointing.

I think I've found the final boss of TypeScript. Here's the error. And nothing else. I know what library causes it, but I have (1) no idea what tsc means here; (2) even less idea how to fix it. Send help.

There is a dichotomy of UI elements. Some elements are a part of your component tree. Cards, form elements, carousels, etc. Some elements don't make much sense as a part of a component tree: toasts, dialogs, alerts. Those are side-effect elements.

Open source friends, if you maintain your project based on public interest on submitted features, please bear in mind it becomes *your* responsibility to bring those features to public's attention. Be so kind to share them then. Don't let great ideas die because nobody saw them.

Man, I wish there were browser context-level assertions in Playwright 😢 await expect(context).toHaveOpenedPage(url) There's no elegant way to know that clicking on an element has triggered a new page to open. I don't want workarounds.

Anyone who has created anything meaningful knows that the most valuable feedback is when somebody points out when you are being wrong.

The "asChild" prop is an accessibility nightmare. It makes it extremely easy to end up with things like <a type="button" role="menu">.

🙋‍♂️ so ... for reasons: I would love to know people's frustrations with: - the current npmjs.com - admin user flows on npm web ui (and cli, locally) 🙏

Beyond grateful to have been selected as the Spotify's FOSS Fund recipient for two years in a row! 🎉 I've got a lot of ideas on how to improve API mocking on the web and support like this is how I'm able to bring those ideas to life. Thank you!

Nobody wants to work in a messy house. This is my philosophy on engineering. When I tackle a feature, I leave it in a functional, complete state. It doesn't mean covering all edge cases but rather finishing every behavior started to its completion.

I don't know how can someone design an editor abstraction and don't have a "get me the selected node(s)" as a first-class utility. Honestly, if you want to learn about API design, dive into any wysiwyg projects out there and you will learn a lot (especially about what not to do).

Looks like my first bug to Chromium got accepted and is currently being worked on. Great to hear! This one breaks the Launch API in PWAs and is crucial to what I'm building.

More people should talk about filenames containing $ being a bad DX since any CLI commands with them will treat $ as a special token and break.

X is such a cesspit at times. It is rather persistent in reminding me about that lately.

"Reveal in Finder" trips me off every time I read it. It's not like my files have been CONCEALED to be revealed. What a poor choice of words. Just use "Show", for goodness sake.

This year, I'd like to see what I can do to improve financial stability of MSW. Governments, banks, and Fortune 500 companies are all using my work while it's one sponsor cancellation away from me not being able to work on it at all. This has to change.

I wonder if this means folks at Nintendo are using MSW. Looks like a thread on some intranet, at the minimum.

Toolbars in WYSIWYG editors can be such a soup of responsibilities, listing actions that effect a text selection, an entire block/element, transform the element, etc. Those do not belong in a single line as those are not siblings semantically.

Do you know why some emitters return a boolean when you emit an event? Because that allows you to know if that event had listeners, i.e. was expected and handled. And craft a proper experience in case it wasn't!

Finland has kickstarted my speaker career way back in the day. Who knows, it might kickstart yours! futurefrontend.com/

I really like signals for collocating data updates with UI updates (or any dependents' updates). When would you ever want to update the data and *not* reflect that in the UI? Signals earn a bonus point of love because you can define them outside of your component tree.

I don't know why, but I read premises to random fantasy books and they all sound like the same book to me. Blurbs are hard.

This is slowly becoming my favorite way of working with events in TypeScript. Strongly-typed, packed with convenience methods like `.emitAsGenerator`, and with actual event flow control even in Node.js! github.com/kettanaito/...

Check out this great write-up about visual regression testing in Playwright 👇 It features a neat built-in API I've learned about recently myself.

This is such a great read! Anyone interested in Solid's best practices, here's a feast for your eyes.

Since making workshops takes some time, I try to stay sharp by trying new tech. Lately, I've tried Remix 3, Solid, and TanStack Start for the first time. All are extremely interesting! I will be writing about some of them in the future. What new things have you tried lately?

Some projects believe that backward compatibility is about supporting bad decisions your userbase made along the way. It is not. You are at the helm of your project. Guide your users. Teach them. Set them up for success through ever API and best practice you encourage.

Proud of the work I did on Playwright Persona. Finally, authentication management in tests is sensible. Describe the roles that can interact with your app and how to authenticate as them. Sessions are stored, invalidated, and recreated automatically. github.com/kettanaito/...

How is it *this* hard to have a tsup/tsdown config that builds two directories into different platforms but lets them import from the /shared directory to prevent identity issues in classes? How is this not the *default* behavior?

Solid.js is fantastic.

What do you think about this analogy for the testing levels? Does this make things a bit more clear to you? 👀

There is software that is honestly such a joy to work with. And then there's software that makes me lose all hope in humanity. What sets them apart is passion in the hearts of those who work on them.

This paragraph makes me extremely sad.

🎟️ JSHeroes tickets are live 🎟️ 👉 jsheroes.io A limited batch of Early Bird tickets is available for €170 - secure the best deal of the season for a 2-day conference with inspiring talks, amazing people, and unforgettable vibes. ✨ See you in May! 🚀 #JSHeroes #TechConference #TechInnovation