react-native-fs migration to @dr.pogodin/react-native-fs

[AjayFrancisTechversant]

Summary

Can someone add a patch or fix for migrating "react-native-fs" to "@dr.pogodin/react-native-fs", since "react-native-fs" is not being well maintained.

What platform(s) does this occur on?

Android, iOS

What workflow(s) does this occur on?

Bare Workflow

Environment (or package.json)

expo-env-info 1.2.1 environment info:
System:
OS: Windows 10 10.0.19045
Binaries:
Node: 22.11.0 - C:\Program Files\nodejs\node.EXE
Yarn: 1.22.22 - ~\AppData\Roaming\npm\yarn.CMD
npm: 10.9.0 - C:\Program Files\nodejs\npm.CMD
SDKs:
Android SDK:
API Levels: 33, 34, 35
Build Tools: 34.0.0, 35.0.0
System Images: android-35 | Google Play Intel x86_64 Atom
IDEs:
Android Studio: AI-242.23339.11.2421.12550806
npmPackages:
react: 18.3.1 => 18.3.1
react-native: 0.75.4 => 0.75.4
Expo Workflow: bare

Your .epub file

No response

Minimal reproducible example

No response

I confirm that i have

• I looked for a solution to my problem in other open and resolved issues
• I checked the examples provided solve my problem
• I have verified that my problem is not caused by a third-party library
• I cloned the project environment examples and still the problem persists
• I'm using the latest available version of the library and its complements

[victorsoares96]

thanks! i'll check this