refactor(image-utils): move to expo/expo

.github/workflows/test.yml

@@ -41,7 +41,6 @@ jobs:
             expo-cli,
             expo-doctor,
             expo-codemod,
-            image-utils,
             pkcs12,
             plist,
             pwa,

.github/workflows/test_windows.yml

@@ -39,7 +39,6 @@ jobs:
             babel-preset-cli,
             expo-cli,
             expo-codemod,
-            image-utils,
             pkcs12,
             plist,
             pwa,

packages/image-utils/README.md

@@ -1,28 +1,3 @@
-<!-- Title -->
-<h1 align="center">
-👋 Welcome to <br><code>@expo/image-utils</code>
-</h1>
+# `@expo/image-utils`
 
-<p align="center">A library for image processing functionality in Expo CLI.</p>
-
-<p align="center">
-  <img src="https://flat.badgen.net/packagephobia/install/@expo/image-utils">
-
-  <a href="https://www.npmjs.com/package/@expo/image-utils">
-    <img src="https://flat.badgen.net/npm/dw/@expo/image-utils" target="_blank" />
-  </a>
-</p>
-
-<!-- Body -->
-
-It uses `sharp` for image processing if it's available through a global `sharp-cli` installation. Otherwise it uses `jimp`, a Node library with no native dependencies, and warns the user that they may want to install `sharp-cli` for faster image processing.
-
-## Advanced Configuration
-
-This package can be configured using the following environment variables.
-
-### EXPO_IMAGE_UTILS_NO_SHARP
-
-When truthy, this will force global `sharp-cli` resolution methods like `isAvailableAsync()` and `findSharpInstanceAsync()` to fail. Other processes can use this to fallback on Jimp for image modifications. By default this is falsy (undefined).
-
-`findSharpInstanceAsync()` will throw an error if disabled because it shouldn't be invoked if `isAvailableAsync()` returns `false`.
+This package has [moved to the `expo/expo` repo](https://github.com/expo/expo/tree/main/packages/%40expo/image-utils).