add troubleshooting about metro Invariant Violation

[radoslawrolka]

📝 Description

example:

1 package may need updating. Run npx expo install --check for details. 
Logs for your project will appear below. Press Ctrl+C to exit. 
<>/react-native-gesture-handler/apps/expo-example/node_modules/@expo/cli/build/src/utils/errors.js:130 throw error; 

Invariant Violation: Detected addition or modification of file node_modules/react-native-screens/.rnrepo-cache/Current, 
but it is tracked as a non-empty directory 
at invariant (<>/react-native-gesture-handler/apps/expo-example/node_modules/invariant/invariant.js:40:15) 
at TreeFS.addOrModify (<>/react-native-gesture-handler/apps/expo-example/node_modules/@expo/metro-file-map/build/lib/TreeFS.js:386:41) 
at Timeout.emitChange [as _onTimeout] (<>/react-native-gesture-handler/apps/expo-example/node_modules/@expo/metro-file-map/build/index.js:580:32) 
at listOnTimeout (node:internal/timers:605:17) 
at process.processTimers (node:internal/timers:541:7) •
 framesToPop: 1 

Node.js v25.8.0 . 

🎯 Type of Change

• 📚 Documentation update

[kmagiera]

Have you tried creating .watchmanconfig under each .rnrepo-cache directory to exclude its content? I think watchman should pick it up and ignore not scan the content. This should be simpler than extending the config

[radoslawrolka]

Watchman only applies the configuration from the project root, so nested .watchmanconfig files are ignored. I’ll remove the .rnrepo-cache exclusion from the troubleshooting section since the fix is usually simple enough (clearing the Metro cache or deleting Watchman state/files).

If someone still runs into persistent issues, ai can add the Watchman exclude configuration too.