Functional component for a modern approach

[finnholland]

Creating a more modern react native module to utilise useState and const statements.

• Added a functional component version of the index.ts to better service modern react native compared to class based.
• Also split out the types into a types.ts so they can be shared across the two files (this is optional but nicer to manage imo)

Wasn't sure on naming conventions so feel free to veto those.
I have tested using my example but will confirm with the example in the package later today.

[Copilot]

Pull Request Overview

This PR refactors the existing class-based AudioRecorderPlayer to extract shared types into types.ts and introduce a functional-hook-based implementation (AudioRecorderPlayerFC), also updating package scripts and dependencies.

• Moved all enums, interfaces, and utility (pad) into a standalone types.ts
• Updated index.ts to import shared types, export both class and functional versions, and added new status getters
• Added a new index.fc.ts file providing a hook-style API, and adjusted lint scripts and dependencies in package.json

Reviewed Changes

Copilot reviewed 5 out of 5 changed files in this pull request and generated 4 comments.

File	Description
types.ts	New shared enums, interfaces, and pad helper export
index.ts	Refactored to import types, export functional API, and added status flags
index.fc.ts	New functional component using React Hooks
package.json	Broadened lint targets, added lint:fix, and included react dependency

Comments suppressed due to low confidence (3)

index.fc.ts:26

• [nitpick] mmss and mmssss are not descriptive. Consider renaming to more explicit names like formatMinutesSeconds and formatMinutesSecondsMilliseconds.

const mmss = (secs: number): string => {

package.json:45

• Adding react as a direct dependency may cause version conflicts for library consumers. Consider moving it to peerDependencies.

"react": "^19.0.0",

index.fc.ts:1

• The new functional implementation lacks accompanying tests. Please add unit tests to cover core behaviors like start/stop recorder/player and getStatus().

import {useState} from 'react';

[Copilot]

The newly added _isStopped and _isFinished fields are never initialized in the constructor, so they default to undefined. Initialize them (e.g., this._isStopped = false; this._isFinished = false;) to avoid unexpected values in getStatus().

Suggested change

	private _isStopped: boolean;
	private _isFinished: boolean;
	private _isStopped: boolean = false;
	private _isFinished: boolean = false;

[Copilot]

Using a local let for _playerCallback will reset on each render. Consider using a useRef to persist the callback across re-renders.

Suggested change

	let _playerCallback: ((event: PlayBackType) => void) | null;
	const _playerCallback = useRef<((event: PlayBackType) => void) | null>(null);

[Copilot]

addPlayBackListener only sets a callback but never subscribes to the native event emitter. You should mirror the subscription logic from startPlayer to ensure events are actually received.

[Copilot]

There's a typo: listerner should be spelled listener.

Suggested change

	* Set listerner from native module for recorder.
	* Set listener from native module for recorder.