@nx/expo 22.2.0-beta.2 → 22.2.0-beta.4

package/src/migrations/update-22-2-0/files/ai-instructions-for-expo-54.md

@@ -0,0 +1,519 @@
+# Expo SDK 54 Migration Instructions for LLM
+
+## Overview
+
+These instructions guide you through migrating an Nx workspace containing Expo projects from Expo SDK 53 to Expo SDK 54. Work systematically through each breaking change category.
+
+## Pre-Migration Checklist
+
+1. **Identify all Expo projects**:
+
+   ```bash
+   nx show projects --with-target start
+   ```
+
+2. **Locate all Expo configuration files**:
+
+   - Search for `app.json` or `app.config.{js,ts}`
+   - Search for `metro.config.{js,ts}`
+   - Check `project.json` files for Expo-related configuration
+
+3. **Identify affected code**:
+
+   - Files importing from `expo-av`
+   - Files importing from `expo-file-system`
+   - Files using `StatusBar` configuration
+   - Android-specific layout code
+   - Files importing from `@expo/vector-icons`
+
+4. **Check for Detox E2E testing projects**:
+   - Search for `detox` in package.json dependencies
+   - Look for `detox.config.js` or `.detoxrc.js` files
+
+## Important Warnings
+
+### Detox E2E Testing Not Supported
+
+**Expo SDK 54 does not currently support Detox for end-to-end testing.** If your workspace includes Detox projects, be aware of the following:
+
+1. **Impact**: E2E tests using Detox will not work after migrating to Expo SDK 54
+2. **Detection**: Check for `detox` in package.json dependencies or projects with `detox.config.js`
+
+**Action Required**: If Detox projects are detected, you MUST ask the user before proceeding:
+
+> "Your workspace contains Detox E2E tests. Detox is not currently supported in Expo SDK 54. Do you want to proceed with the migration knowing that Detox tests will not work until Detox adds SDK 54 support?"
+
+**Alternatives to consider**:
+
+- Stay on Expo SDK 53 if Detox E2E testing is critical for your workflow
+- Wait for Detox to add Expo SDK 54 support
+- Consider migrating to [Maestro](https://maestro.mobile.dev/) for E2E testing (has Expo SDK 54 support)
+
+## Migration Steps by Category
+
+### 1. expo-av to expo-audio and expo-video Migration
+
+The `expo-av` package has been deprecated and split into two separate packages: `expo-audio` and `expo-video`.
+
+#### 1.1 Audio Migration
+
+**Search Pattern**: `import.*from ['"]expo-av['"]` with `Audio` usage
+
+**Changes Required**:
+
+```typescript
+// BEFORE (Expo SDK 53)
+import { Audio } from 'expo-av';
+
+const sound = new Audio.Sound();
+await sound.loadAsync(require('./audio.mp3'));
+await sound.playAsync();
+
+// AFTER (Expo SDK 54)
+import { useAudioPlayer } from 'expo-audio';
+
+function AudioComponent() {
+  const player = useAudioPlayer(require('./audio.mp3'));
+
+  const play = () => player.play();
+  const pause = () => player.pause();
+
+  return <Button onPress={play} title="Play" />;
+}
+```
+
+**Action Items**:
+
+- [ ] Install `expo-audio`: `npx expo install expo-audio`
+- [ ] Remove `expo-av` if only used for audio
+- [ ] Replace `Audio.Sound` with `useAudioPlayer` hook
+- [ ] Replace `Audio.Recording` with `useAudioRecorder` hook
+- [ ] Update audio playback control methods (`playAsync` -> `play`, etc.)
+- [ ] Convert class-based audio handling to hook-based approach
+
+#### 1.2 Video Migration
+
+**Search Pattern**: `import.*from ['"]expo-av['"]` with `Video` usage
+
+**Changes Required**:
+
+```tsx
+// BEFORE (Expo SDK 53)
+import { Video } from 'expo-av';
+
+function VideoPlayer() {
+  return (
+    <Video
+      source={{ uri: 'https://example.com/video.mp4' }}
+      style={{ width: 300, height: 200 }}
+      useNativeControls
+      resizeMode="contain"
+    />
+  );
+}
+
+// AFTER (Expo SDK 54)
+import { VideoView, useVideoPlayer } from 'expo-video';
+
+function VideoPlayer() {
+  const player = useVideoPlayer('https://example.com/video.mp4', (player) => {
+    player.loop = true;
+    player.play();
+  });
+
+  return (
+    <VideoView
+      player={player}
+      style={{ width: 300, height: 200 }}
+      nativeControls
+      contentFit="contain"
+    />
+  );
+}
+```
+
+**Action Items**:
+
+- [ ] Install `expo-video`: `npx expo install expo-video`
+- [ ] Remove `expo-av` if only used for video
+- [ ] Replace `Video` component with `VideoView` and `useVideoPlayer`
+- [ ] Replace `resizeMode` prop with `contentFit`
+- [ ] Replace `useNativeControls` prop with `nativeControls`
+- [ ] Update video control methods to use the player instance
+
+### 2. expo-file-system Import Path Changes
+
+**Search Pattern**: `import.*from ['"]expo-file-system/next['"]`
+
+**Changes Required**:
+
+```typescript
+// BEFORE (Expo SDK 53)
+import { File, Directory } from 'expo-file-system/next';
+
+// AFTER (Expo SDK 54)
+import { File, Directory } from 'expo-file-system';
+```
+
+**Action Items**:
+
+- [ ] Replace all `expo-file-system/next` imports with `expo-file-system`
+- [ ] Verify API compatibility (the API is now stable)
+
+### 3. StatusBar Configuration Removal
+
+In Expo SDK 54, the `expo-status-bar` configuration is now handled differently. The old `userInterfaceStyle` in `app.json` affects status bar theming.
+
+**Search Pattern**: `userInterfaceStyle` in `app.json` or `app.config.*`
+
+**Changes Required**:
+
+```json
+// BEFORE (Expo SDK 53)
+{
+  "expo": {
+    "userInterfaceStyle": "automatic",
+    "ios": {
+      "userInterfaceStyle": "light"
+    },
+    "android": {
+      "userInterfaceStyle": "dark"
+    }
+  }
+}
+
+// AFTER (Expo SDK 54)
+// The userInterfaceStyle is now handled via expo-system-ui
+// For programmatic control, use:
+```
+
+```typescript
+// AFTER (Expo SDK 54) - Programmatic control
+import * as SystemUI from 'expo-system-ui';
+
+// Set root view background color
+SystemUI.setBackgroundColorAsync('#ffffff');
+```
+
+**Action Items**:
+
+- [ ] Install `expo-system-ui`: `npx expo install expo-system-ui`
+- [ ] Review `userInterfaceStyle` settings in app.json
+- [ ] Move UI style handling to `expo-system-ui` if programmatic control is needed
+
+### 4. Android Edge-to-Edge UI
+
+Expo SDK 54 enables edge-to-edge display by default on Android. This means content can extend behind system bars (status bar and navigation bar).
+
+**Search Pattern**: Android-specific styles, safe area handling, padding/margin adjustments
+
+**Changes Required**:
+
+```tsx
+// BEFORE (Expo SDK 53) - Implicit safe area
+function App() {
+  return (
+    <View style={{ flex: 1 }}>
+      <Text>Content</Text>
+    </View>
+  );
+}
+
+// AFTER (Expo SDK 54) - Explicit safe area handling
+import { SafeAreaView } from 'react-native-safe-area-context';
+// or
+import { useSafeAreaInsets } from 'react-native-safe-area-context';
+
+function App() {
+  return (
+    <SafeAreaView style={{ flex: 1 }}>
+      <Text>Content</Text>
+    </SafeAreaView>
+  );
+}
+
+// Or with hooks for more control
+function App() {
+  const insets = useSafeAreaInsets();
+
+  return (
+    <View
+      style={{ flex: 1, paddingTop: insets.top, paddingBottom: insets.bottom }}
+    >
+      <Text>Content</Text>
+    </View>
+  );
+}
+```
+
+**Action Items**:
+
+- [ ] Audit all screen components for safe area handling
+- [ ] Install `react-native-safe-area-context` if not present
+- [ ] Wrap root components with `SafeAreaProvider`
+- [ ] Add `SafeAreaView` or use `useSafeAreaInsets` where content touches screen edges
+- [ ] Test on Android devices/emulators to verify UI doesn't overlap system bars
+- [ ] Pay special attention to:
+  - Header components
+  - Bottom navigation/tab bars
+  - Modal components
+  - Full-screen media players
+
+### 5. React Native Reanimated Version Decision
+
+Expo SDK 54 supports both Reanimated v3 and v4. If you're using New Architecture, you should upgrade to v4.
+
+**Search Pattern**: `react-native-reanimated` in package.json, worklet functions
+
+**Reanimated v3 (stable)**:
+
+```bash
+npx expo install react-native-reanimated@3
+```
+
+**Reanimated v4 (recommended for New Architecture)**:
+
+```bash
+npx expo install react-native-reanimated@4
+```
+
+**Action Items**:
+
+- [ ] Check if New Architecture is enabled in your project
+- [ ] If using New Architecture, upgrade to Reanimated v4
+- [ ] If staying on old architecture, Reanimated v3 is fine
+- [ ] Test all animations after the upgrade
+
+### 6. @expo/vector-icons Validation
+
+Some icons in `@expo/vector-icons` may have been renamed or removed in SDK 54.
+
+**Search Pattern**: `import.*from ['"]@expo/vector-icons['"]`
+
+**Action Items**:
+
+- [ ] Run the app and check console for warnings about missing icons
+- [ ] Search for icon names that may have changed
+- [ ] Update icon names as needed
+- [ ] Consider using the Expo Vector Icons directory to find replacements: https://icons.expo.fyi/
+
+### 7. React 19.1 Compatibility
+
+Expo SDK 54 uses React 19.1 and React Native 0.81.
+
+**Search Pattern**: `React.FC`, deprecated lifecycle methods, legacy context API
+
+**Changes Required**:
+
+```typescript
+// BEFORE - React.FC (discouraged in React 19)
+const MyComponent: React.FC<Props> = ({ title }) => {
+  return <Text>{title}</Text>;
+};
+
+// AFTER - Direct function typing
+function MyComponent({ title }: Props) {
+  return <Text>{title}</Text>;
+}
+
+// Or with explicit return type
+const MyComponent = ({ title }: Props): React.ReactElement => {
+  return <Text>{title}</Text>;
+};
+```
+
+**Action Items**:
+
+- [ ] Update TypeScript types for React 19.1 (`@types/react@~19.1.0`)
+- [ ] Remove usage of `React.FC` pattern (optional but recommended)
+- [ ] Check for deprecated lifecycle methods and update to hooks
+- [ ] Verify third-party libraries are compatible with React 19.1
+
+### 8. Metro Configuration Updates
+
+Expo SDK 54 uses Metro 0.83 with updated configuration.
+
+**Search Pattern**: `metro.config.{js,ts}`
+
+**Changes Required**:
+
+```javascript
+// BEFORE (Expo SDK 53)
+const { getDefaultConfig } = require('@expo/metro-config');
+
+const config = getDefaultConfig(__dirname);
+
+// AFTER (Expo SDK 54) - Same API, but verify compatibility
+const { getDefaultConfig } = require('@expo/metro-config');
+
+const config = getDefaultConfig(__dirname);
+
+// Ensure any custom transformers are compatible with Metro 0.83
+```
+
+**Action Items**:
+
+- [ ] Update `@expo/metro-config` to `~0.22.0`
+- [ ] Update `metro-config` to `~0.83.0`
+- [ ] Update `metro-resolver` to `~0.83.0`
+- [ ] Test custom Metro plugins/transformers for compatibility
+
+### 9. Babel Configuration Cleanup
+
+Expo SDK 54 updates to `babel-preset-expo@~14.0.0`.
+
+**Search Pattern**: `babel.config.js`, `.babelrc`
+
+**Action Items**:
+
+- [ ] Update `babel-preset-expo` to `~14.0.0`
+- [ ] Remove any deprecated Babel plugins
+- [ ] Clear Metro cache after Babel changes: `npx expo start --clear`
+
+## Post-Migration Validation
+
+### 1. Clear All Caches
+
+```bash
+# Clear Expo cache
+npx expo start --clear
+
+# Clear Metro bundler cache
+rm -rf node_modules/.cache/metro-*
+
+# Clear Nx cache if needed
+nx reset
+```
+
+### 2. Run Tests Per Project
+
+```bash
+# Test each project individually
+nx run-many -t test -p PROJECT_NAME
+```
+
+### 3. Run All Tests
+
+```bash
+# Run tests across all affected projects
+nx affected -t test
+```
+
+### 4. Test on Device/Simulator
+
+```bash
+# iOS
+nx run PROJECT_NAME:run-ios
+
+# Android
+nx run PROJECT_NAME:run-android
+```
+
+### 5. Review Migration Checklist
+
+- [ ] All `expo-av` usages migrated to `expo-audio` or `expo-video`
+- [ ] All `expo-file-system/next` imports updated
+- [ ] Safe area handling verified on Android
+- [ ] All icon references validated
+- [ ] React 19.1 compatibility verified
+- [ ] Metro and Babel configurations updated
+- [ ] All tests pass
+- [ ] App runs on iOS simulator/device
+- [ ] App runs on Android emulator/device
+
+## Common Issues and Solutions
+
+### Issue: Audio playback stops when component unmounts
+
+**Solution**: The new `useAudioPlayer` hook manages cleanup automatically. If you need persistent audio, consider using a context or state management solution.
+
+### Issue: Video player shows black screen
+
+**Solution**: Ensure you're using `useVideoPlayer` with `VideoView`. Check that the video source URL is correct and accessible.
+
+### Issue: Content hidden behind Android navigation bar
+
+**Solution**: Wrap your screen content with `SafeAreaView` from `react-native-safe-area-context` or use `useSafeAreaInsets` for custom padding.
+
+### Issue: Missing icons after upgrade
+
+**Solution**: Check the Expo Vector Icons directory for renamed icons: https://icons.expo.fyi/
+
+### Issue: TypeScript errors with React 19.1
+
+**Solution**: Update `@types/react` to `~19.1.0` and check for deprecated patterns.
+
+### Issue: Metro bundler fails to start
+
+**Solution**: Clear all caches with `npx expo start --clear` and ensure Metro packages are at compatible versions.
+
+## Files to Review
+
+Create a checklist of all files that need review:
+
+```bash
+# Configuration files
+find . -name "app.json" -o -name "app.config.*"
+find . -name "metro.config.*"
+find . -name "babel.config.*"
+
+# Files with expo-av imports
+rg "from ['\"]expo-av['\"]" --type ts --type tsx --type js
+
+# Files with expo-file-system/next imports
+rg "from ['\"]expo-file-system/next['\"]" --type ts --type tsx --type js
+
+# Files with vector-icons imports
+rg "from ['\"]@expo/vector-icons['\"]" --type ts --type tsx --type js
+
+# Safe area related files
+rg "SafeAreaView|useSafeAreaInsets" --type ts --type tsx --type js
+```
+
+## Migration Strategy for Large Workspaces
+
+1. **Migrate in phases**: Start with a small project, validate, then expand
+2. **Use feature branches**: Create separate branches for different migration aspects
+3. **Run tests frequently**: After each configuration change, run affected tests
+4. **Document issues**: Keep track of project-specific issues and solutions
+5. **Test on real devices**: Android edge-to-edge changes require device testing
+
+## Useful Commands During Migration
+
+```bash
+# Find all Expo projects
+nx show projects --with-target start
+
+# Run specific project
+nx start PROJECT_NAME
+
+# Test specific project after changes
+nx test PROJECT_NAME
+
+# Test all affected
+nx affected -t test
+
+# View project details
+nx show project PROJECT_NAME --web
+
+# Clear Nx cache if needed
+nx reset
+
+# Clear Expo cache
+npx expo start --clear
+```
+
+---
+
+## Notes for LLM Execution
+
+When executing this migration:
+
+1. **Work systematically**: Complete one category before moving to the next
+2. **Test after each change**: Don't batch all changes without validation
+3. **Keep user informed**: Report progress through each section
+4. **Handle errors promptly**: If tests fail, fix immediately before proceeding
+5. **Update documentation**: Note any workspace-specific patterns or issues
+6. **Create meaningful commits**: Group related changes together with clear messages
+7. **Use TodoWrite tool**: Track migration progress for visibility
+8. **Test on both platforms**: Expo changes often affect iOS and Android differently

package/src/migrations/update-22-2-0/update-jest-for-expo-54.d.ts

@@ -0,0 +1,12 @@
+import { Tree } from '@nx/devkit';
+/**
+ * Update Jest configuration for Expo SDK 54.
+ *
+ * Expo 54 requires a different approach for Jest configuration:
+ * - Remove the custom resolver from jest.config
+ * - Delete the jest.resolver.js file
+ * - Add ImportMetaRegistry mock and structuredClone polyfill to test-setup.ts
+ * - Update tsconfig files to remove jest.resolver.js references
+ */
+export default function update(tree: Tree): Promise<void>;
+//# sourceMappingURL=update-jest-for-expo-54.d.ts.map

package/src/migrations/update-22-2-0/update-jest-for-expo-54.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"update-jest-for-expo-54.d.ts","sourceRoot":"","sources":["../../../../../../packages/expo/src/migrations/update-22-2-0/update-jest-for-expo-54.ts"],"names":[],"mappings":"AAAA,OAAO,EACL,IAAI,EAOL,MAAM,YAAY,CAAC;AAIpB;;;;;;;;GAQG;AACH,wBAA8B,MAAM,CAAC,IAAI,EAAE,IAAI,iBA6C9C"}

package/src/migrations/update-22-2-0/update-jest-for-expo-54.js

@@ -0,0 +1,150 @@
+"use strict";
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.default = update;
+const devkit_1 = require("@nx/devkit");
+const jest_1 = require("@nx/jest");
+const path_1 = require("path");
+/**
+ * Update Jest configuration for Expo SDK 54.
+ *
+ * Expo 54 requires a different approach for Jest configuration:
+ * - Remove the custom resolver from jest.config
+ * - Delete the jest.resolver.js file
+ * - Add ImportMetaRegistry mock and structuredClone polyfill to test-setup.ts
+ * - Update tsconfig files to remove jest.resolver.js references
+ */
+async function update(tree) {
+    const projects = (0, devkit_1.getProjects)(tree);
+    for (const [projectName, config] of projects.entries()) {
+        if (!isExpoProject(tree, config.root)) {
+            continue;
+        }
+        // Check if this project has Jest configured
+        const jestConfigPath = findJestConfigPath(tree, config.root);
+        if (!jestConfigPath) {
+            continue;
+        }
+        const jestConfigContent = tree.read(jestConfigPath, 'utf-8');
+        // Only process if this is an Expo project with jest-expo preset and custom resolver
+        if (!jestConfigContent.includes('jest-expo') ||
+            !jestConfigContent.includes('jest.resolver.js')) {
+            continue;
+        }
+        // Remove resolver property from jest.config using AST
+        (0, jest_1.removePropertyFromJestConfig)(tree, jestConfigPath, 'resolver');
+        // Delete jest.resolver.js file
+        const resolverPath = (0, path_1.join)(config.root, 'jest.resolver.js');
+        if (tree.exists(resolverPath)) {
+            tree.delete(resolverPath);
+        }
+        // Update test-setup.ts with new mocks
+        updateTestSetup(tree, config.root);
+        // Update tsconfig files to remove jest.resolver.js references
+        updateTsConfigFilesForV54(tree, config.root);
+        devkit_1.logger.info(`Updated Jest configuration for ${projectName} to support Expo SDK 54`);
+    }
+    await (0, devkit_1.formatFiles)(tree);
+}
+function findJestConfigPath(tree, projectRoot) {
+    const possiblePaths = [
+        (0, path_1.join)(projectRoot, 'jest.config.ts'),
+        (0, path_1.join)(projectRoot, 'jest.config.cts'),
+        (0, path_1.join)(projectRoot, 'jest.config.js'),
+    ];
+    for (const configPath of possiblePaths) {
+        if (tree.exists(configPath)) {
+            return configPath;
+        }
+    }
+    return null;
+}
+function updateTestSetup(tree, projectRoot) {
+    const testSetupTsPath = (0, path_1.join)(projectRoot, 'src/test-setup.ts');
+    const testSetupJsPath = (0, path_1.join)(projectRoot, 'src/test-setup.js');
+    let testSetupPath = testSetupTsPath;
+    if (!tree.exists(testSetupTsPath)) {
+        if (tree.exists(testSetupJsPath)) {
+            testSetupPath = testSetupJsPath;
+        }
+        else {
+            // Create test-setup.ts if it doesn't exist
+            tree.write(testSetupPath, '');
+        }
+    }
+    let existingContent = tree.read(testSetupPath, 'utf-8') || '';
+    // Add ImportMetaRegistry mock if not already present
+    if (!existingContent.includes('ImportMetaRegistry')) {
+        const importMetaRegistryMock = `jest.mock('expo/src/winter/ImportMetaRegistry', () => ({
+  ImportMetaRegistry: {
+    get url() {
+      return null;
+    },
+  },
+}));
+
+`;
+        existingContent = importMetaRegistryMock + existingContent;
+    }
+    // Add structuredClone polyfill if not already present
+    if (!existingContent.includes('structuredClone')) {
+        const structuredClonePolyfill = `if (typeof global.structuredClone === 'undefined') {
+  global.structuredClone = (object) => JSON.parse(JSON.stringify(object));
+}
+`;
+        existingContent = existingContent + '\n' + structuredClonePolyfill;
+    }
+    tree.write(testSetupPath, existingContent);
+}
+function updateTsConfigFilesForV54(tree, projectRoot) {
+    // Update main tsconfig (app or lib) to remove jest.resolver.js from excludes
+    const mainTsConfigFiles = [
+        'tsconfig.app.json',
+        'tsconfig.lib.json',
+        'tsconfig.json',
+    ];
+    for (const configFile of mainTsConfigFiles) {
+        const configPath = (0, path_1.join)(projectRoot, configFile);
+        if (tree.exists(configPath)) {
+            try {
+                (0, devkit_1.updateJson)(tree, configPath, (json) => {
+                    if (json.exclude && Array.isArray(json.exclude)) {
+                        json.exclude = json.exclude.filter((item) => item !== 'jest.resolver.js');
+                    }
+                    return json;
+                });
+            }
+            catch {
+                // Skip if JSON is invalid
+            }
+            break;
+        }
+    }
+    // Update tsconfig.spec.json to remove jest.resolver.js from includes
+    const specTsConfigPath = (0, path_1.join)(projectRoot, 'tsconfig.spec.json');
+    if (tree.exists(specTsConfigPath)) {
+        try {
+            (0, devkit_1.updateJson)(tree, specTsConfigPath, (json) => {
+                if (json.include && Array.isArray(json.include)) {
+                    json.include = json.include.filter((item) => item !== 'jest.resolver.js');
+                }
+                return json;
+            });
+        }
+        catch {
+            // Skip if JSON is invalid
+        }
+    }
+}
+function isExpoProject(tree, projectRoot) {
+    const packageJsonPath = (0, devkit_1.joinPathFragments)(projectRoot, 'package.json');
+    if (!tree.exists(packageJsonPath)) {
+        return false;
+    }
+    try {
+        const packageJson = (0, devkit_1.readJson)(tree, packageJsonPath);
+        return Boolean(packageJson.dependencies?.expo || packageJson.devDependencies?.expo);
+    }
+    catch {
+        return false;
+    }
+}

package/src/utils/ensure-dependencies.d.ts

@@ -1,3 +1,3 @@
 import { type GeneratorCallback, type Tree } from '@nx/devkit';
-export declare function ensureDependencies(host: Tree, unitTestRunner: 'jest' | 'none'): GeneratorCallback;
+export declare function ensureDependencies(host: Tree, unitTestRunner: 'jest' | 'none'): Promise<GeneratorCallback>;
 //# sourceMappingURL=ensure-dependencies.d.ts.map

package/src/utils/ensure-dependencies.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"ensure-dependencies.d.ts","sourceRoot":"","sources":["../../../../../packages/expo/src/utils/ensure-dependencies.ts"],"names":[],"mappings":"AAAA,OAAO,EAGL,KAAK,iBAAiB,EACtB,KAAK,IAAI,EACV,MAAM,YAAY,CAAC;AAiBpB,wBAAgB,kBAAkB,CAChC,IAAI,EAAE,IAAI,EACV,cAAc,EAAE,MAAM,GAAG,MAAM,GAC9B,iBAAiB,CA+BnB"}
+{"version":3,"file":"ensure-dependencies.d.ts","sourceRoot":"","sources":["../../../../../packages/expo/src/utils/ensure-dependencies.ts"],"names":[],"mappings":"AAAA,OAAO,EAGL,KAAK,iBAAiB,EACtB,KAAK,IAAI,EACV,MAAM,YAAY,CAAC;AAGpB,wBAAsB,kBAAkB,CACtC,IAAI,EAAE,IAAI,EACV,cAAc,EAAE,MAAM,GAAG,MAAM,GAC9B,OAAO,CAAC,iBAAiB,CAAC,CAiC5B"}