Community Drives the Ecosystem Forward

Hi,

Today, I'd like to talk about community contributions. In the past couple of weeks, several PRs from community contributors landed across my projects. I think this is worth sharing.

Zustand v5.0.11

I released Zustand v5.0.11 on February 1st. It is a patch release, but all three fixes came from community contributors.

The devtools middleware got better typing. The persist middleware was fixed to not rely on the global localStorage directly. This matters in environments where localStorage is not available. And the immer middleware typing was improved for the slices pattern.

None of these are flashy changes. They are the kind of improvements that quietly make a library more reliable.

I should also mention v5.0.10, which included a fix for a race condition during concurrent rehydrate calls in the persist middleware. That PR required patience from the contributor, who waited through the review process. The result is solid.

Excalidraw Animate

Someone submitted Playwright E2E tests for excalidraw-animate. I requested some changes during review. After the fixes, I merged it. It is good to see testing infrastructure being added to this project by someone other than me.

Waku

In Waku, a new contributor made their first contribution by fixing middleware auto-discovery to exclude test files. A Spanish-language learning resource was contributed and merged. And a Netlify dynamic routes bug was fixed by a community member.

Why This Matters

I maintain these projects, but I cannot catch everything. Middleware edge cases, test infrastructure, documentation in other languages. These contributions come from people using the libraries in ways I do not. That is what makes open source better than what any single developer can do.

If you want to contribute to any of these projects, there are always open discussions and issues to work on. Do not hesitate.

Happy coding.