-
Notifications
You must be signed in to change notification settings - Fork 786
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
⚠ Please archive this repository and link to the new fork ⚠ #863
Comments
That is valid feedback. While we use this library extensively for our core products and have ambitions of revitalizing and improving it, during the last few years our organization hasn't had the resources to regularly maintain or upgrade the package. On and off I've brought it up that we need to either dedicate resources, find a new maintainer, or archive it. The conversation never really goes anywhere. I'll bring it up again and push a little harder on a final decision. Thank you for the feedback. |
Many thanks for your answer, much appreciated. It would be nice if the package can start being maintained again but indeed that represents a lot work |
@rpenfold I would be very happy to add you or some others of your company as maintainer to my fork and we work on the lib together! |
This updates rn-fetch-blob to a version with one cherry-picked commit atop the v0.11.2 we were previously using: zulip/rn-fetch-blob@e17b2a51c The rn-fetch-blob package itself is no longer maintained: joltup/rn-fetch-blob#863 There's a fork that is maintained, `react-native-blob-util`: https://npmjs.com/package/react-native-blob-util That fork addressed the Android 14 requirement to set an explicit RECEIVER_EXPORTED flag (zulip#5903), merging a fix: RonRadtke/react-native-blob-util#303 RonRadtke/react-native-blob-util#306 Our fix is cherry-picked from that one. (If this app weren't a legacy codebase in maintenance mode, we'd take the time to upgrade this dependency more generally, probably switching to the react-native-blob-util fork. As is, we'll skip that and use the time to focus on completing the new Flutter app.) Fixes: zulip#5903
This updates rn-fetch-blob to a version with one cherry-picked commit atop the v0.11.2 we were previously using: zulip/rn-fetch-blob@e17b2a51c The rn-fetch-blob package itself is no longer maintained: joltup/rn-fetch-blob#863 There's a fork that is maintained, `react-native-blob-util`: https://npmjs.com/package/react-native-blob-util That fork addressed the Android 14 requirement to set an explicit RECEIVER_EXPORTED flag (#5903), merging a fix: RonRadtke/react-native-blob-util#303 RonRadtke/react-native-blob-util#306 Our fix is cherry-picked from that one. (If this app weren't a legacy codebase in maintenance mode, we'd take the time to upgrade this dependency more generally, probably switching to the react-native-blob-util fork. As is, we'll skip that and use the time to focus on completing the new Flutter app.) Fixes: #5903
Joltup, when you forked the original
react-native-fech-blob
package the owner of the repo agreed to archive it and link to your project.Now that you have abandoned the project too, please have the same courtesy - archive it and link to the latest fork, probably https://github.com/RonRadtke/react-native-blob-util/
This ensures that developers don't waste time implementing your package or creating pull requests that you will never merge, and ensures that the active fork gets the attention it deserves (and the pull requests and donations).
Tagging the last committer @rpenfold
The text was updated successfully, but these errors were encountered: