
Grab your gear: The official Sanity swag store
Read Grab your gear: The official Sanity swag storeI'd be happy to help, but I need a bit more context about the specific errors you're seeing! Since you mentioned you just added a plugin, here are the most common issues that come up:
Most Common Plugin-Related Errors:
Dependency version conflicts - This is super common, especially with @sanity/ui mismatches. Plugins might depend on different versions than your Studio. Try running:
npm install
# or
yarn installSchema/type errors - If the plugin adds new field types, you might see "unnamed type" or "unknown type" errors. Make sure you've:
sanity.config.ts (or sanity.config.js)plugins arrayCORS errors - If you're seeing API connection errors, you might need to add your localhost to allowed origins:
sanity cors add http://localhost:3333Module not found errors - Sometimes the plugin isn't fully installed. Try:
npm install [plugin-name]
sanity startQuick troubleshooting steps:
node_modules and reinstall: rm -rf node_modules && npm install.sanity folder if it existsIf you can share the specific error messages you're seeing (either from the browser console or terminal), I or others in the community can give you much more targeted help! Things like "TypeError", "Cannot find module", specific error codes, or stack traces would be really useful to diagnose the exact issue.
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.
Content operations
Content backend


The only platform powering content operations
By Industry


Tecovas strengthens their customer connections
Build and Share

Grab your gear: The official Sanity swag store
Read Grab your gear: The official Sanity swag store