
Grab your gear: The official Sanity swag store
Read Grab your gear: The official Sanity swag storeThis error isn't actually a Sanity-specific issue—it's a general JavaScript dependency compatibility problem between framer-motion and framesync packages that's occurring in your Gatsby build process. While you're working on a Sanity + Gatsby monorepo, this particular error is related to your bundler's dependency resolution, not Sanity itself.
The error message "export 'flushSync' was not found in 'framesync'" indicates that framer-motion is trying to import a function that doesn't exist in the version of framesync that's currently installed. This typically happens when there's a version mismatch between these two packages.
Quick fixes to try:
rm -rf node_modules yarn.lock
yarn installpackage.json:{
"resolutions": {
"framesync": "^6.1.0",
"framer-motion": "^10.16.0"
}
}yarn why framer-motion
yarn why framesyncSince this is a general bundler/dependency issue rather than a Sanity problem, you might get better help in these communities:
The Sanity community focuses on content modeling, GROQ queries, Studio customization, and Sanity-specific integrations. For build tooling and dependency resolution issues like this one, the framework-specific communities will have more expertise to help you troubleshoot.
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