Team member of @vite.dev and @vitest.dev
- @voidzero.dev (@cloudflare.social)
📍 Berlin, Germany

@vladimir.berlin
Team member of @vite.dev and @vitest.dev
- @voidzero.dev (@cloudflare.social)
📍 Berlin, Germany
🙋♂️ so, what are the git forges you are using - or want to be using? asking for … reasons. (would appreciate sharing for reach)
It’s sad to see Deno being discontinued. However, I think it’s not all terrible. Deno pushed server side JS forward for everyone - Node copied many the standout features Deno had at launch in 2020, bringing them to the masses. Fetch, web sockets, web crypto, direct TypeScript execution, and more. 🫡
If the cost of generating and maintaining code is going down, open source projects should double down on community, people, helping their dependencies and upstream teams, building trust that they are good stewards of that piece of the ecosystem. Some are sadly going in the opposite direction.
You can renew your OSS Anthropic subscription using the same form 😄
20 years ago, Anna Politkovskaya was murdered for speaking truth to power in Putin’s Russia. She exposed the brutality of war. She gave a voice to its victims. And she refused to be intimidated into silence. This cost her life. But her memory is carried by so many to this day.
If you'd like to contribute to an oss project, don't focus on creating PRs. Help the maintainers triage issues and review existing PRs. Test beta releases, and give feedback about new APIs and features. Join the community and be around to help others. They need your care way more than your code now.
we don't look at closed prs until someone from the team works on a linked issue
with prs open, the list just grows infinitely because there is not enough time and resources to deal with them
what changes is how much is in my face at all times. github ui is my work station, unrelated PRs are similar to an unorganised desk - they steal the attention when I need to focus with the new approach I take the agency back and can deal with issues+prs combination on my own pace
I think adding friction is good. Help us triage the issue first so we approve your contribution instead of the other way around
the problem is not just AI slop, it's the constant stream of PRs that demand your attention. even if the content is ok, we need to review it first. after you review it, there is another new PR with no end in sight it was always like this, just not on this scale that it's impossible to ignore
yep. we have a board with issues we want to work on
didn’t lock it, it’s more of an approve-first approach rather than just leaving all PRs open for an eventual review PRs are still there, they are just closed
If you have a contributor role, then yes. But approved list is a separate thing
We are updating our AI Policy to reduce maintenance stress. All pull requests are now automatically closed, unless they are created by maintainers or users from an approved list of contributors. The PR is not lost. If the team decides the change is worth pursuing, we will reopen it.
@typescript.fm podcast hosted me and my Oxc compadre Cameron talking type-aware linting, compilers, what VoidZero's acquisition means for Vite, and what the future of tooling might look like in the age of LLMs. A really fun conversation. typescript.fm/bonus83
With MSW 3.0 released this week, I want to try something new to make the project financially sustainable. I wrote an open letter about the project, its history, and impact on the ecosystem.
I ask for five minutes of your time to read it. Thank you.
mswjs.io/sponsor
Cancelled my Cursor subscription and finally started to sponsor @svelte.dev
Cancelled Apple Music / TV and finally started to sponsor @kettanaito.com
Thank you for the nudge and inspiration @santoshyadav.dev
so sorry to hear! this sucks 😔
I'm excited to announce MSW v3.0! 🥳
- Leaner dependency graph and smaller size;
- ESM-only;
- Granular entrypoints;
- GraphQL subscriptions;
- Socket-based network interception in Node.js;
- And much more!