Now when usinjg the @expo/webpack-config, we get a warning

Error: The project entry file could not be resolved. Please either define it in the `package.json` (main), `app.json` (expo.entryPoint), create an `index.js`, or install the `expo` package.

A workaround is to just put an empty index.js at the root of your project, or yarn add expo (even if you won't use it)

This gatsby plugin (and thus the @expo/webpack-config) can be used with plain RNW. User might not always want to use Expo SDK web apis.

I see 2 solutions:

• @expo/webpack-config should allow to bypass this warning (I guess it can make sense for NextJS integration too)
• This gatsby plugin could fallback to another webpack config if expo dependency is not found (seems not ideal, as expo config does some useful things we want to keep)

@EvanBacon any idea how this should be handled?