Open edkeohane opened 3 years ago
I lowered the react version back to 16.14.0 and the error went away. There's something about react 17 that is breaking this.
Upgrade Gatsby to 2.32.6 works for me.
Had similar issues, resolved by running "npm update gatsby-cli" in web directory as noted here: https://github.com/gatsbyjs/gatsby/issues/19827
Tried the set up for local development after getting the cloud environments working. https://www.sanity.io/create?template=sanity-io/sanity-template-gatsby-blog
2021-02-11T19_01_15_484Z-debug.log.txt