metro.config.js

/**
 * Metro configuration for React Native
 * https://github.com/facebook/react-native
 *
 * @format
 */

const path = require('path');

const exclusionList = require('metro-config/src/defaults/exclusionList');

const blockList = exclusionList([
  /node_modules\/.*\/node_modules\/react-native\/.*/,

  // Workaround for `EPERM: operation not permitted, lstat '~\midl-MIDLRT-cl.read.1.tlog'`
  /.*\.tlog/,

  // This stops "react-native run-windows" from causing the metro server to
  // crash if its already running
  new RegExp(`${path.join(__dirname, 'windows').replace(/[/\\]+/g, '/')}.*`),

  // Workaround for `EBUSY: resource busy or locked, open '~\msbuild.ProjectImports.zip'`
  /.*\.ProjectImports\.zip/,
]);

/**
 * This config is a bit exotic because our example app is not its own package
 * (that would require setting this repo up as a monorepo). We need to tell
 * Metro that the root of the project is our `example` folder (`projectRoot`),
 * and that it should look for modules in repo root (`watchFolders`) as this is
 * where the `node_modules` folder lives. Metro will otherwise fail to resolve
 * anything.
 */
const config = {
  projectRoot: path.join(__dirname, 'example'),
  watchFolders: [__dirname],
  resolver: {
    blockList,
    // for some reason, since 73 metro does not see this
    extraNodeModules: {
      '@vonovak/react-native-theme-control': __dirname,
    },
  },
};
const { getDefaultConfig, mergeConfig } = require('@react-native/metro-config');
module.exports = mergeConfig(getDefaultConfig(__dirname), config);