GitHub comment by Rich-Harris: Bumping this — can we please get this merged @bmeurer? Or are we going to have to fork it? This isn't a dependency that people want to use, it's one that people are effectively forced to use by the design decisions Chrome took around automatic workspaces, so it would be greatly appreciated if we could keep it up to date

vite-plugin-devtools-json still depends on Vite v7, and the maintainer isn't merging the v8 PR, it's been a month.

@rich-harris.dev summarized the problem with the plugin itself really well — nobody wants to use it in the first place 😅 we have to.

I'm currently not into RSC yet because the only stable implementation is still in a single framework which I don't care for.

I think I'll eventually end up diving into another UI library, now that JSX became more popular. I love JSX 🥰

Expiring Soon: 3 Free Months of Apple Music

I know that you really want me to get a subscription, Apple, but this red color is really harsh. People often internally call it “danger”, so let’s save it for something that’s actually wrong.

TIL that worktrees can live inside repos, not just outside 🤦‍♂️

Btw, excuse the subtitles offset, the tech is not playing nice together, I need the figure out at which point.

What's happening to macOS? I manage to break the cursor just by hovering over the Finder app.

Learn a11y test queries — it’s not hard, it’s more accurate and powerful, and it starts getting you thinking about a11y.

Vite Plus seems like a really interesting approach that both abstracts away a lot of boilerplate while maintaining the same level of freedom as a tailor made setup.

The idea used to freak me out due to just how much it can do, but all of the hairy stuff is optional (like managing Node versions).

WhatsApp search bar with query “foo” on the left and Meta AI “Ask” button on the right

Meta, I see that in WhatsApp you replaced the search field’s clear button with your AI “Ask” button.

The clear button is a strongly established UI pattern, so I’m going to play a little guessing game — nobody wants your AI thing, so now you’re trying to trick people into at least visiting it.

Yesssssss, I really wanted this!

freeform crosswalk-looking thing painted on the road

Don’t get cute with traffic markings and signals — I genuinely didn’t know whether it was okay to cross here, but at least they had fun painting this.

Great article 👌 now I finally read up about this API, where and how much of it is available all in one place

Svelte is the goat…? I need to brush up on my English skills

Great news! 😍

Companies are gambling at this point. If you can, please speak up inside your company so they up their open source strategy and commit (more) funds to make our shared commons sustainable. We're going to lose it all. Funding dynamics in OSS need to change. Fast.

For debugging Browser Mode UI is pretty good, but I can’t hover through my test steps like in Playwright UI.

I need to focus on one test at a time, the UI is only showing me the current/last stage of the last test I ran.

I know about --trace, but that’s more for CI.

Great news about slow tests!

I generally prefer terminal output and headless Browser Mode.

Vitest CLI accepts both --ui and --browser.headless=false, I find this a little unclear in the context of Browser Mode.

And not really being sure whether to also install @vitest/ui.

Scary. It was not theirs, yet they chose to use the code anyway to create a derivative.

How did you come up with the name of the library? If you're willing to share. I think "Elena" is a Macedonian name.

Btw, I like the future-facing approach that Elena is taking on the web components, like defaulting to light DOM, also that it's not relying on experimental syntax like decorators.

Btw, suggestions are exhausting, I’m also here to help. If you agree with any of these, I can work on your selection of these suggestions.

- add StackBlitz examples, so that people can feel how easy it is right there from the browser

That’s all what comes to mind for now. I don’t know if that would make an impact, those are my obervations imagining myself as a newcomer because mocking is such a tricky subject.

- start the implementation example with a fetch() call to ease people into it
- after the implementation make it known that the fetch() will now return the mocked response
- the vertical lines in the “Integrate Anywhere” section confused me about which image refers to which subsection

- show mocking the MODULE that’s making the API request, briefly explaining the downsides of that
- display a new illustration explaining the flow where MSW fits into that

Unfortunately this would imply that MSW is only for testing frameworks, but it also helps a lot IMO.

GitHub - kettanaito/async-history-stack: Arbitrary change history management in JavaScript. Arbitrary change history management in JavaScript. - kettanaito/async-history-stack

Excited to open source Async History Stack: an undo/redo system I've been using for a while.

⏳ Async-friendly
🚫 Abortable entries
🚦 Merges, batches, chained operations
🌱 Works with anything

github.com/kettanaito/...

Do you think that could help?

That came to mind because I feel like there’s some resistance against learning MSW despite people knowing it exists. I feel like people think it’s more complicated than it is.

Do you think that people who are complaining didn’t know about MSW?

There are wrinkles in adopting MSW in my team, but those are also not the best examples of average dev…

I learned MSW myself a long time ago from Kent C. Dodds…

I think the homepage could give a cleaner overview of what MSW does, and activate people from there. I can offer suggestions with that.

You can immediately tell by its in-your-face nature that it's not here give something, it's here to TAKE.

And it's really jarring among the UI that actually works for the purpose it implies to be intended for.

It happened — in Google Meet I accidentally clicked "Ask Gemini" because the dropdown opens on hover rather than click.

The more I tried to close, to more things popped open, I just wanted to talk to my coworkers! I found the close button… then the hover-dropdown opened again 🤦‍♂️

I hate AI UI.