Issue with crashing after updating Sanity CLI, resolved by removing a part implementation in sanity.json.

Hi there. I just updated sanity cli to v.2.13.1 and I'm having this strange issue. I'm trying to edit some articles (or create new ones) locally, but the whole thing crashes. I can't for the life of me figure out exactly what causes it, could this be a Sanity bug with the latest update?

Hi Kristoffer, could you try removing your

node_modules

folder and

package-lock.json

+

yarn.lock

files before running

npm install

and starting the studio once more?

I already did, but for good measure I'll try again!

Sorry , the problem still occurs! Also checked for other updates with the

yarn upgrade-interactive --latest

command, but everything should be up to date

We just released a new version of the studio a few moments ago (

v2.14.0

) - could you try to upgrade once more to see if that helps? If not, we'll dig deeper 🙂
--
Upgrade the Command Line Interface (CLI) with:

(or with yarn)

Upgrade the Sanity Studio with:

Ayy, I had such big hopes, but still a no-go! I'm not quite sure where to start debugging this, most of the studio stuff is out of the box

Are you using any custom input components or plugins? Please feel free to share the plugins array of your

sanity.json

file here.

Thanks for sharing 🙂 It might be related to the

media-library

in this case. However, one more thing to check: are you using any custom asset sources that you know of?
For example, an implementation that includes:

Not that I'm aware of, only similar thing I can find is in the

sanity.json

file:
Not sure if that is the same as importing into a component?

Yes, I believe that's relevant here. Could you test if the issue persists when taking out that part implementation?

That seemed to do the trick! So what am I missing here? I didn't start the project myself, and I've mostly worked on the web side of it until now. Lots to learn 😅

I'm afraid you've discovered a bug here 🙂 We'll try to reproduce it on our end and see if we can get a fix out. In the meantime, please let me know if you run into any issues or are missing a custom asset source implementation you were expecting to be there.

Alright, thanks a bunch for all the help!

i.e. when adding images to a document, custom asset sources let you pull in images from external sources such as Cloudinary, Unsplash, etc.