fix: TVOSExample metro config

TVOSExample/metro.config.js

@@ -1,5 +1,12 @@
 const { getDefaultConfig, mergeConfig } = require('@react-native/metro-config');
 
+/**
+ * Metro configuration
+ * https://reactnative.dev/docs/metro
+ *
+ * @type {import('metro-config').MetroConfig}
+ */
+
 const fs = require('fs');
 const path = require('path');
 const exclusionList = require('metro-config/src/defaults/exclusionList');
@@ -13,6 +20,7 @@ const rnsRoot = path.resolve(__dirname, '..');
 
 const modules = [
   '@react-navigation/native',
+  '@react-navigation/stack',
   'react-native-reanimated',
   'react-native-safe-area-context',
   'react-native-gesture-handler',
@@ -30,7 +38,6 @@ const config = {
   // We need to make sure that only one version is loaded for peerDependencies
   // So we exclude them at the root, and alias them to the versions in example's node_modules
   resolver: {
-    sourceExts: ['ts', 'tsx', 'js', 'jsx', 'json'],
     blockList: exclusionList(
       modules.map(
         m =>
@@ -51,12 +58,6 @@ const config = {
     // to various errors. To mitigate this we define below custom request resolver, hijacking requests to conflicting modules and manually
     // resolving appropriate files. **Most likely** this can be achieved by proper usage of blockList but I found this method working ¯\_(ツ)_/¯
     resolveRequest: (context, moduleName, platform) => {
-      if (moduleName.startsWith('@react-navigation')) {
-        // For some reason, react-navigation packages don't want to resolve from
-        // the project's node_modules, so we need to use standard Metro resolver.
-        return context.resolveRequest(context, moduleName, platform);
-      }
-
       if (moduleName === 'react-native-screens') {
         return {
           filePath: path.join(rnsRoot, 'src', 'index.tsx'),