Errors after upgrading Sanity from 3.15.1 to 3.16.0 with @sanity/vision
I understand the frustration of getting errors after upgrading! While I don't have access to the specific desk structure entries you mentioned in the thread, I can help you troubleshoot common issues that occur when upgrading from Sanity 3.15.1 to 3.16.0.
Based on the 3.16.0 release notes, this version focused mainly on Portable Text improvements, Unicode support, and bugfixes. However, there was one notable bugfix that might be relevant:
Key bugfix in 3.16.0: "Fixed a bug that caused specifying apiVersion on documentList() and documentTypeList() to not work in the desk structure."
This means if your desk structure uses documentList() or documentTypeList() with an apiVersion parameter, the behavior changed in 3.16.0 - it now actually works as intended, whereas before it was being ignored.
Common troubleshooting steps:
Check your
apiVersionusage: If you're usingapiVersionin your desk structure functions, the fix in 3.16.0 might now be enforcing it where it wasn't before.Clear your Studio cache: Sometimes upgrade issues are cache-related:
rm -rf node_modules/.sanity npm run devCheck for TypeScript errors: If you're using TypeScript, run
npm run buildto see if there are type errors that might not show up in dev mode.Review import paths: Make sure your desk structure imports are correct for v3.
If you can share the specific error messages or the desk structure code that's failing, I'd be happy to provide more targeted help! The error messages usually give good clues about what's breaking.
Show original thread10 replies
Sanity – Build the way you think, not the way your CMS thinks
Sanity is the developer-first content operating system that gives you complete control. Schema-as-code, GROQ queries, and real-time APIs mean no more workarounds or waiting for deployments. Free to start, scale as you grow.