You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Get the following error immediately after clone, install, and setup on my machine running Windows 10:
"Multiple "root" queries found: "BlogIndexQuery" and "BlogIndexQuery".
Only the first ("BlogIndexQuery") will be registered. ERROR #85910"
Which doesn't make any sense at all because there is only one BlogIndexQuery in the GraphQL request. Run dev has a hard time reading the project files properly on windows it looks like.
Very similar to this issue within the context of a different Gatsby project. Tried all of the solutions given on this thread to no avail: gatsbyjs/gatsby#19863
This works fine on my mac which is great, but I'm just wondering why this doesn't seem to be very Windows friendly.
The text was updated successfully, but these errors were encountered:
@taylorbakow thanks for reporting this. Unfortunately, I don't have a windows machine at hand. :/ An investigation and maybe a PR would be much appreciated. 😊
@taylorbakow thanks for reporting this. Unfortunately, I don't have a windows machine at hand. :/ An investigation and maybe a PR would be much appreciated. 😊
Get the following error immediately after clone, install, and setup on my machine running Windows 10:
"Multiple "root" queries found: "BlogIndexQuery" and "BlogIndexQuery".
Only the first ("BlogIndexQuery") will be registered. ERROR #85910"
Which doesn't make any sense at all because there is only one BlogIndexQuery in the GraphQL request. Run dev has a hard time reading the project files properly on windows it looks like.
Very similar to this issue within the context of a different Gatsby project. Tried all of the solutions given on this thread to no avail: gatsbyjs/gatsby#19863
This works fine on my mac which is great, but I'm just wondering why this doesn't seem to be very Windows friendly.
The text was updated successfully, but these errors were encountered: