@antfu.me
A ship in harbor is safe, but that is not what ships are built for. creator → @sli.dev • @unocss.dev • @vueuse.org • @vitest.dev • elk.zone core team → @nuxt.com • @vite.dev • vuejs.org maintainer → @shiki.style • eslint.style he/him → antfu.me
simply, more OSS projects should DO THIS.
OSS is a long playing game, if not forever. but we are people behind those projects, and we need good rest and balance to keep things sustainable. I am super happy to see this move and looking forward to see how it could change how OSS works for all of us.
I am trying both Cursor and Claude Code
late to the party. I have finally been convinced by multiple awesome developers to give agents another try.
this is my first premature contribution:
github.com/antfu/skills
if people no longer read the code, API is no longer targeting humans, is there still a need for "good API design"? is it still worth the effort to figure out what would be the best for users, instead of the best of ai to understand/use? I don't know.
for a little bit of context, I build tools for humans for better dx or productivity, and I consider it a creative work, so I am not worried at all about "being replaced by ai"
what I am concerned is the tools' target users. if people no longer care about user-experience but more on "ai-experience"
🫂
do people still care?
is it still relevant?
License This project is not licensed under an open-source license and is the intellectual property of Tailwind Labs Inc. The source is available only as an educational resource and to accept fixes for minor mistakes.
TIL that the tailwinds docs are not open source. It is the first time I see a popular OSS project with this kind of non-license approach for their docs. Are there other examples out there? Maybe I missed them too assuming that docs followed the same license as their code.
Yes, for a while longer, I am sorry about that:
bsky.app/profile/antf...
😇❓
I am trying, but everytime they do it with different account 😇
Don't even know if I should build some LLM-powered tools to fight back magic with magic, or if I should just quit altogether.
Agents create the illusion that you can accomplish complicated work with simple prompts, and people become less appreciative of the hard work behind the scenes.
I feel bad that I have to enable this for @shiki.style, as I am getting AI-bot-accounts creating the same issues again and again, and sending PRs trying to "fix" the same thing. I don't know if that repo has been somehow labeled as "AI playground" or something, but I can't keep bearing with it.
I certainly don't want to act rudely or terribly to any human contributors and make the environment worse, but I also don't want to waste my time being nice and supportive to AI bots.
I feel the dilemma is, that I feel responsible for being friendly and welcoming to make the experience nicer for newcomers to OSS, who may not yet know the manner well.
But with AI messing this up, it's really hard to tell if it's a human behind I should take care or just AI doing terrible work.
a GitHub PR titled `fix(adobe): handle provider configuration objects properly` with the following text: 🐛 Bug Fix Potentially fixes Adobe font-face declaration generation regression introduced in v0.12.1. Closes #736 ⚠️ Note: This fix was developed with AI assistance This PR was blindly developed by AI, without me having deep any knowledge of @nuxt/fonts internals. While it's (claimed by Claude to) been tested and appears (again, according to Claude) to work correctly, a thorough review by @danielroe or someone familiar with the fontless/unifont architecture would be appreciated.
I actually love this disclaimer
I am burning out on this...
Multiple PRs created by AI-bot accounts are trying to solve the same issue that has not yet even been identified, with verbose plain-text PR descriptions.
I don't even know if I should bother to reply...
Any ways to stop this? 😇
npm downloads chart of pacakge @antfu/eslint-config, generated by https://npm.chart.dev/@antfu/eslint-config
Didn't even think that my personal ESLint config deserves so many downloads, 1M/mo 🫨. Thank you all!
That's an interesting approach. To me personally, I don't think I would restrict anyone from using any tools they think would be helpful, including agents or anything, as long as they do a self-review. More like I want to see opinions from people, rather than the LLM's results as-is.
I want to think that teaching OSS etiquette as part of regular education would help devs empathize with maintainers and understand when a PR is actually helpful. GitHub could guide new users too. But spam will likely worsen significantly. Platforms need to find ways to remain usable in the long term
My first advice to junior contributors is to STOP using vibe coding for PRs. OSS is always about people more than about code. We don't need more code generated by LLM, we need more people who care.
My first advice to junior contributors is to STOP using vibe coding for PRs. OSS is always about people more than about code. We don't need more code generated by LLM, we need more people who care.
Vibe coding PRs - STOP please...
💖 This Sep & Oct, we have forwarded our Open Collective fund to support
@zyyv.dev
webfansplz
@bluwy.me
@bikari.top
@9romise.bsky.social
@e18e.dev
@esm.sh
@pnpm.io
@cyberalien.dev
Join us to show appreciation for our dependencies and help them be sustainable!
opencollective.com/antfu/update...
tsdown v0.16.0 is out now, featuring Vite DevTools integration!
Just install `@vitejs/devtools` and run `tsdown --debug` for an early preview.
Big thanks to @antfu.me, @arlo7.me, and @hyf0.bsky.social for their help!
If you use @sli.dev within a monorepo, you might want to try this project by Leo Chiu!
github.com/leochiu-a/sl...
Anthony Fu on stage at VueFes Japan
Last but not least, we had @antfu.me test the capacities of the venue by drawing a huge crowd for his first ever conference talk in Japanese!
His presentation envisioned a future where Vite DevTools make it trivial to introspect your applications - powered by an ecosystem built on DevTools Kit
