Error: The project entry file could not be resolved. about gatsby-plugin-react-native-web HOT 9 OPEN

Hi, just wanted to let you know that latest beta is likely more stable and you should not need to configure anything on your side.

from gatsby-plugin-react-native-web.

Thanks guys, you're amazing! 😄

from gatsby-plugin-react-native-web.

it seems to be working on 2.0.0-beta.0

from gatsby-plugin-react-native-web.

I encountered this error and was able to bypass using a blank index.js file in the project root. However I am now getting:

Error: It appears like Gatsby is misconfigured. Gatsby related graphql calls are supposed to only be evaluated at compile time, and then compiled away. Unfortunately, something went wrong and the query was left in the compiled code.

Has anyone seen this issue using this plugin?

from gatsby-plugin-react-native-web.

Solved it using the solution offered by @slorber in #23

from gatsby-plugin-react-native-web.

yeah sorry about that, I can't really make this automatic for now, need some modifications in expo webpack config

from gatsby-plugin-react-native-web.

@felippepuhle 2.0 is more stable but has not the Expo webpack config so you'll have to hack yourself to make the project work if you are using external RNW compatible dependencies. Will try to make 3.0 more stable soon so that everything works fine out of the box.

from gatsby-plugin-react-native-web.

In fact I'm using 3.0.0-beta.0 and it's working with babel-preset-expo

from gatsby-plugin-react-native-web.

I can work on a fix. What is the main entry point that Webpack should resolve to?

from gatsby-plugin-react-native-web.