Anthony Fu

📝 New blog post!

Open source is becoming more challenging for me over time. I have written down some of my experiences and what I learned on my journey.

Would love to hear what you think in the comments!
https://antfu.me/posts/mental-health-oss

Too much work to do, and don't have time to make proper release announcements. Let me batch them together for the releases in the recent two weeks 😉

💚 Nuxt DevTools v1.3: New components tree & props view
🌈 Shiki v1.5: 10+ new grammars, better CloudFlare support
▶️ Slidev v0.49: Draggable elements, context Menu, custom routes, v-switch, brand new VS Code Extension
😀 Nuxt Icon v1.0-beta: SSR-friendly, more efficient new approach
🔘 UnoCSS v0.60: Custom reasons for blocklist, better directives
💙 ESLint Stylistic v2.0: Bump ts-eslint and rewrite tests
🪄 Shiki Magic Move v0.4: Svelte components
💖 Sponsorkit v0.14: Circles render, merge sponsors across platforms
✨ New pkg - eslint-plugin-command: On-demand micro-codemod
✨ New pkg - eslint-vitest-rule-tester: Tester for ESLint v9

🙏 Huge thanks to @webfansplz@mas.to @kermanx@mastodon.social
**Hiroshi Ogawa** @chris_zhu@mas.to **Kisaragi Hiu **and other contributors for their awesome work!

Enjoy! 🚀

💖 These two months, we redistributed our funds to **Kevin Deng, Harlan Wilton, KazariEX, Fabian Hiller, MSW, pnpm, Iconify** for their amazing work!

🙏 Thanks to **logto.io** and all the sponsors for making this possible!

https://opencollective.com/antfu/updates/anthony-fu-fund-redistribution-september-and-october-2024

💖 New blog post! Let's Forward the Sponsorship to our dependencies!

https://antfu.me/posts/sponsorship-forwarding

💖 These two months, we redistributed our funds to **Marco Ippolito**, @johnsoncodehk@m.webtoo.ls, @eslint@fosstodon.org, libvips, CSSTree, Discovery.js, @pnpm@fosstodon.org, Iconify for their amazing work!

🙏 Thanks to **logto.io** and all the sponsors for making this possible!

https://opencollective.com/antfu/updates/anthony-fu-fund-redistribution-july-and-august-2024

💖 This month, we redistributed our collective funds to @tseslint@fosstodon.org, unifiedjs, @pnpm@fosstodon.org, vis.js, Tresjs and SVGO, to thanks their amazing work!

🙏 Thanks to **logto.io**, @kissu@mas.to, and all the sponsors for making this possible!

👇 Full announcement:
https://opencollective.com/antfu/updates/anthony-fu-fund-redistribution-june-2024

This month, we redistributed our collective funds to Iconify and markdown-it to thank their work for the ecosystem! 💖

Read the full update with the link below. At the end of every month, we will share an update like this with you!
https://opencollective.com/antfu/updates/anthony-collective-redistribution-april-2024

Now in @rollupjs@m.webtoo.ls v3.24.0, `#__NO_SIDE_EFFECTS__` annotation is supported to mark function declarations as side-effects free. You might not need to add `#__PURE__` to every call anymore, while providing more optimized bundles!

Thanks a lot to @lukastaegert@m.webtoo.ls's great support and fast release!

https://github.com/rollup/rollup/pull/5024

I don't have a good idea in mind yet, but I think we should find an organic way to **higher the barrier of creating new issues** on OSS projects.

Currently, everyone can sign up to GitHub and create spam issues in 5mins. Wasting maintainers' time to read and manage them.

The issue forms help a bit, but easy to be ignored. A bot, or AI, to verify the content and auto-close might also help to some extent. However, it still creates notifications.

I think it would be better to verify/filter out unqualified issues **before been created.**

@phessler@bsd.network @elk@m.webtoo.ls Hi! I would like to know how do you define "inappropriately". We are just a client, which all it knows is the data from the Mastodon's API. If there is any field from the API indicates your preference on directing or not displaying, we are happy to implement that and solve your issue. But if not, I don't think we could make Elk to treat your content specially.