margelo / margelo/react-native-nitro-sqlite
Handle Metro process failures before readiness
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 565
- Forks
- 53
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 18
Description
The macOS runner in PR #298 attaches its child-process error listener after waiting for Metro readiness. A spawn error can therefore escape the runner's normal failure handling.
Attach failure monitoring immediately, race readiness against process failure, and verify that startup failures and cleanup complete without unhandled rejections.
Source: https://github.com/margelo/react-native-nitro-sqlite/pull/298
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.
Research direction
Start by reviewing PR #298 and the macOS runner's Metro startup path, focusing on when the child-process error listener is attached relative to readiness. Exercise a startup failure and confirm that readiness races process failure and cleanup completes without unhandled rejections.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react-native
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 56/100