flow

To implement a react-native-audio-api feature, follow a 9-step PR checklist covering Web Audio API spec review, TypeScript interfaces, C++ AudioNode development, HostObject wiring, tests, and documentation before submitting your pull request.

The end-to-end workflow for shipping C++ AudioNodes involves writing native C++ nodes, wiring HostObjects, adding TypeScript classes, updating TurboModule specs, and running C++ and JS tests to ensure complete integration.

To fix a bug in react-native-audio-api without regressions, reproduce the issue, perform root-cause analysis, apply the fix, and update pitfall notes during the post-mortem step to document the resolved vulnerability.

TurboModule spec updates are not required for every react-native-audio-api feature; they are only needed when the specific feature demands new native module bindings alongside standard TypeScript and C++ changes.

The best way to ensure deliverables are complete before a react-native-audio-api PR is to apply a structured 9-step checklist that satisfies requirements for clear ownership, reproducible steps, and integration with QA checks.

You need to write TypeScript interfaces for a React Native audio bug fix when the resolution modifies the existing API surface, requiring updates to TypeScript classes and documentation alongside the native C++ corrections.