Require cycles are allowed, but can result in uninitialized values. Consider refactoring to remove the need for a cycle.

[HardMode2015]

Require cycles are allowed, but can result in uninitialized values. Consider refactoring to remove the need for a cycle. Require cycle: node_modules/@ui-kitten/components/index.js -> node_modules/@ui-kitten/components/ui/index.js -> node_modules/@ui-kitten/components/ui/circularProgressBar/circularProgressBar.component.js -> node_modules/@ui-kitten/components/index.js

using expo 49

[iamursky]

Same here for Expo 50.

[velsa]

Same for expo 50.0.14

[moza88]

applies to "expo": "~50.0.17",

[stelmakhivan]

Not sure it's good, but such metro config helped me with required cycles (I use react-native and have added expo packages)

const { getDefaultConfig } = require('expo/metro-config');
const { mergeConfig } = require('@react-native/metro-config');

/**
 * Metro configuration
 * https://facebook.github.io/metro/docs/configuration
 *
 * @type {import('metro-config').MetroConfig}
 */
const config = {
  resolver: {
    // Add patterns to ignore require cycles for node_modules and src directory
    requireCycleIgnorePatterns: [
      /node_modules\/.*/,
      /src\/.*/,
    ],
  },
};

module.exports = mergeConfig(getDefaultConfig(__dirname), config);