Error with gatsby-source-sanity v7.6.0, revert to v7.5.1 for now

Hi, I just recently updated to Gatsby v5 and gatsby-source-sanity to v7.6.0. But when I start up the development server I get an error.
It’s and error #11321. You can checkout the screenshot below.

Hey 👋I got this error this morning, it has been raised as an issue on
GitHub , best option is to revert to

7.5.1

for the time being

This is currently not working with Gatsby 4 as well. We were on gatsby-source-sanity 7.0.4. Upgraded to 7.5.1 to test and it still didn’t work. Running gatsby version 4.24.4. Is this an Sanity issue or a Gatsby issue?

Hey , in my case I'm using Gatsby

5.1.0

I had to run

npm uninstall gatsby-source-sanity

and re-install

npm i gatsby-source-sanity@7.5.1

in order to downgrade and update my package-lock.json file. Once fully downloaded, this error goes away.

Hey thanks for that :) sorry for the cross channel posting but looks like Sanity is also aware and working with gatsby on a fix :) https://sanity-io-land.slack.com/archives/C9Z7RC3V1/p1669345406618619?thread_ts=1669345406.618619&cid=C9Z7RC3V1

Ah just ran into is, grateful it's not just me 😅

Same here, but all of my love and support to and team!

Since I had it set to ^7.5.1 in my npm package file, it picked up 7.6.0 on Gatsby cloud preview and broke everything. Maybe Sanity should made the new version ^8.0.0, just like all of the Gatsby plugins do that they maintain--aligning major versions with their releases, even if the change isn't that big, since the plugin 100% depends on Gatsby to work correctly.

Great idea 💡

Gatsby is actively pursuing this and would be grateful for a minimal repro project or steps that produces the behaviour

It's me, Dustin from Gatsby! Yes, we'd love to get this fixed but first we need to identify the problem.
If anyone has a Sanity site (ideally a simplified one) and a way we could reproduce it, we'd love to help all of you by addressing the fix. I don't
think it's related to Gatsby 5 (since apparently the issue persists on Gatsby 4?).
You can feel free to chime in on this issue and/or DM me or e-mail me at
dustin@gatsbyjs.com .

https://github.com/sanity-io/gatsby-source-sanity/issues/200

If helpful, we have a reasonably handy guide for simplified reproductions (which tend to get a little more complicated with CMSs). https://gatsby.dev/reproduction

I wonder if the Sanity/Gatsby blog starter has this problem--I can try this tonight. It's simply an install and then npm upgrade to 7.6.0

Been chatting with Dustin and even but just for transparencies sake of this channel, I have created a basic repo with the bug here: https://github.com/taulal/gatsby-source-sanity-bug-repo 🙂

We have opened an internal bug on this and are getting our team on it. Thank you Taylor for the simplified reproduction!!

We have fixed the issue and opened a PR for the Sanity team to review!

https://github.com/sanity-io/gatsby-source-sanity/pull/207
(It was a regression due to a version bump in the plugin of Axios)

Amazing Dustin thank you and the team heaps! :)

Ha, always one of the underlying packages! awesome work!