Implemented Workarounds

Three workarounds are implemented to fix issues. In the future once these packages are fixed we may be able to remove the patches.

1. We use the patch-package to deal with this issue: victory-native-xl#333. Issue lies in how Victory Native exports components. The issue does not break functionality, but throws annoying warnings in the console. To fix this issue as of June 8, 2025 we use this solution here. Steps taken:

   1a In node_modules/victory-native/package.json fix the lines as indicated in the linked comment.

   1b. Run npx patch-package victory-native --exclude 'nothing'. It's important to include the --exlude as by default package.json changes are usually ignored.

   1c. In the app's package.json's scripts add "postinstall": "patch-package"

   1d. Commit the changes. See here: https://www.npmjs.com/package/patch-package#set-up

2. We are over-riding the version of @shopify/react-native-skia used by victory-native 2.0.0-next.4 - see here: victory-native-xl#556.

3. Expo-Doctor may throw a ✖ Validate packages against React Native Directory package metadata error for new dependencies. To add exceptions wepackage.json. The packages are added to expo.doctor.reactNativeDirectoryCheck.exclude list. Add more as follows:

"expo": {
    "doctor": {
      "reactNativeDirectoryCheck": {
        "exclude": [
          "react-native-element-dropdown",
          "moment",
          "react-native-orientation-locker",
          "moment",
          "react-native-navigation-bar",
          "react-navigation",
          "react-navigation-stack",
          "tailwindcss",
          "luxon",
          ...more packages here..
        ]
      }
    }
  },