skills.rest
strataga
stratagaCOMMUNITY
Explore all skills by this author →
Website𝕏@jcochranioGitHub

expo-file-system-class-api-migration

Migrate legacy expo-file-system API calls to File, Directory, and Paths classes.

Updated Jan 24, 2026
Search Tags:#typescript#migration#expo#expo-file-system#sdk52#class-based-api
One-click install
npx skills add https://github.com/strataga/claude-setup --skill expo-file-system-class-api-migration
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: expo-file-system-class-api-migration
Source: https://github.com/strataga/claude-setup/tree/main/skills/expo-file-system-class-api-migration
Command: npx skills add https://github.com/strataga/claude-setup --skill expo-file-system-class-api-migration

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Migrates legacy expo-file-system usage to the new class-based API to fix breakages introduced in Expo SDK 52+.

Core Features & Use Cases

  • Transition imports to import { File, Directory, Paths } from 'expo-file-system'
  • Replace legacy operations with class-based equivalents (File, Directory, Paths)
  • Use in projects upgrading Expo SDK 52+ to stabilize file-system interactions

Quick Start

Start by replacing legacy expo-file-system calls with the new class-based API (File, Directory, Paths) and run a TypeScript check.

Frequently Asked Questions about expo-file-system-class-api-migration

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I migrate expo-file-system to the class-based API in SDK 52?▼

Expo SDK 52 introduced breakages by deprecating legacy expo-file-system functions. Migrating to the class-based API using File, Directory, and Paths classes stabilizes file-system interactions and resolves compatibility issues when upgrading your project.

What is the class-based API for expo-file-system?▼

Yes, you can use the expo-file-system class-based API with TypeScript. The migration process validates TypeScript types when replacing legacy API calls with File, Directory, and Paths class equivalents, ensuring type safety for file deletion and info retrieval operations.

How do I replace legacy expo-file-system calls with File and Directory classes?▼

Use the expo-file-system class-based API migration when upgrading projects to Expo SDK 52 or later. It specifically addresses file-system interaction breakages introduced in SDK 52+ by transitioning legacy imports to File, Directory, and Paths classes.

Does expo-file-system class API migration support path caching and info retrieval?▼

If your expo-file-system migration is not working, verify that all imports are updated to 'expo-file-system' classes (File, Directory, Paths) and that legacy API calls for file deletion and info retrieval are replaced with class-based equivalents. Run a TypeScript check to catch type errors.

Related Skills

Explore More Software Engineering Skills→
karr83sv2k25-aikarr83sv2k25-ai

react-native-expo

Upgrade React Native Expo apps across SDK 52-54 with New Architecture guidance.

Community
Advanced
MiDouTechMiDouTech

fix-unused-imports

Remove unused TypeScript imports and variables causing TS6133 errors.

Official
Intermediate
SovranBitcoinSovranBitcoin
23

react-native-expo

Migrate Expo React Native apps to SDK 52-54 with New Architecture.

Official
Advanced
growthxaigrowthxai

flow-convert-workflow-definition

Convert Flow SDK workflow classes to Output SDK workflow() functions.

Official
Advanced