margelo / margelo/react-native-nitro-fetch
[TODO] Clean up repository
Open
@Szymon20000 is already working on this.
Since Sep 22, 2025.
- Dominant language
- C++
- Stars
- 997
- Forks
- 50
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 14
Description
We need to clean up the repository a bit.
- Move everything into a
package/orpackages/react-native-nitro-fetchfolder so the root is clean (file list is too long, we can't see the README on first glance - check out https://github.com/mrousavy/nitro for reference) - Remove the git commit hooks - those suck. Instead, move them into CI. See https://github.com/mrousavy/nitro/tree/main/.github/workflows
- Add CI actions to run typescript & nitrogen
- Add CI actions to build the example app
- Remove any dependencies that we don't use (e.g. commitlint)
- Add cleaner issue templates like in Nitro (e.g.: https://github.com/mrousavy/nitro/tree/main/.github/ISSUE_TEMPLATE)
- Migrate to a monorepo (bun?)
- Remove all
prepare_....shscripts for Cronet downloads as those are unused (it should be in Gradle scripts so contributors dont have to run extra scripts when they want to clone the repo) - Migrate away from MMKV to
NSUserDefaults/SharedPreferences(MMKV is not needed and could break, let's keep it simple!) - Remove
// @ts-ignorestatements and actually make the types sound (noascasts, instead do safe type casts - otherwise this will break in the future) - Remove
console.warnif something is not available (e.g.react-native-mmkvimport), instead expose something likesupportsPrefetching(we don't need that since it always works once we migrate away from MMKV) - Remove all
console.logs - those were probably for debugging only. Any errors should bethrow new Error(...) - Refactor all
any/unknowntypes to at least something more concrete (e.g.interface Worklets { runOnJS(..): void }instead of just having itany)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.