[x] I've ensured the unit and smoke tests are still passing - either by running yarn test:unit and yarn test:smoke:[ios|android] or by checking the appropriate CircleCI builds' statuses.
[ ] I've manually tested whether the changes I made work as expected.
Motivation and Context
With LegacyEject deleted in expo-cli, there's no reason to keep this code in the expo-cli repo. Having it in expo-cli means any kind of change will result in a full republish of expo-cli. This code is also adding a lot of bloat to expo-cli.
Description
First, I copied over the modules from expo/xdl that are only used in turtle V1. Then I updated the lint.
A couple modules will still be imported from xdl (for now) until we can find a good compromise for sharing them with expo-cli. These modules are: UserManager, AndroidCredentials, Versions, EmbeddedAssets, UrlUtils, Api.
After this PR lands, I'll open a PR to remove the copied modules from @expo/xdl.
Checklist
yarn test:unitandyarn test:smoke:[ios|android]or by checking the appropriate CircleCI builds' statuses.Motivation and Context
With LegacyEject deleted in expo-cli, there's no reason to keep this code in the expo-cli repo. Having it in expo-cli means any kind of change will result in a full republish of expo-cli. This code is also adding a lot of bloat to expo-cli.
Description
First, I copied over the modules from expo/xdl that are only used in turtle V1. Then I updated the lint.
A couple modules will still be imported from xdl (for now) until we can find a good compromise for sharing them with expo-cli. These modules are:
UserManager, AndroidCredentials, Versions, EmbeddedAssets, UrlUtils, Api.After this PR lands, I'll open a PR to remove the copied modules from
@expo/xdl.