-
Notifications
You must be signed in to change notification settings - Fork 52
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
What's the maintenance status? #59
Comments
Yes please, I have same doubt has tscneid, |
Would be really nice if @paol-imi could open this up to new maintainers so PRs can be merged. In the meantime, this fork by @Secretmapper seems to have the most fixes on it: https://github.com/Secretmapper/muuri-react/tree/strict-muuri-0.9 I took that and merged to master and fixed package.json and it's here: https://github.com/adamerose/muuri-react |
absolute legend - thanks for saving my project. |
Hello everyone, unfortunately muuri-react has not been updated for several years and there has been no community action, the muuri-react example no longer works on the latest version of React, so I have rebuilt a library muuri for react that does not depend on any version of React or muuri, depending on the version of your project depending on the version of If you want to run muuri in React 17 or React 18, you can try this library Happy coding! |
@paol-imi This is an amazing library and I'm grateful that you spent your time developing it! Could you please elaborate on your plans to work on it in the future?
Looking at the current open issues and activity, I couldn't help but notice that there are some long-awaited missing features, such as compatibility with React 17 or the latest versions of Muuri. I myself am considering migrating away from
muuri-react
right now because of this.I absolutely understand and respect that OSS maintainers move on and spend their time with different things and projects.
Still, IMHO, it would benefit the community to make a clear statement about the maintenance status of this project. If we knew that you're not planning on working on it in the near future, you and us could take the according actions.
For example, you could look for a new (co-)maintainer, link to a community-maintained fork, or even consider taking money for further development.
What do you think? Would be great to hear from you! Thanks!
The text was updated successfully, but these errors were encountered: