Uncaught error

[mkalsi25]

I create new sanity project npm create sanity, install, run npm run start locally. Got error.

Uncaught error: Only two keyframes currently supported with spring and inertia animations. Trying to animate 0,0,1 http://localhost:3333/node_modules/.sanity/vite/deps/chunk-ORQM2G6B.js?v=8999f3cb:16718:15 Error: Only two keyframes currently supported with spring and inertia animations. Trying to animate 0,0,1 at invariant (http://localhost:3333/node_modules/.sanity/vite/deps/chunk-VKDBORTS.js?v=8999f3cb:6432:13) at MainThreadAnimation.initPlayback (http://localhost:3333/node_modules/.sanity/vite/deps/chunk-VKDBORTS.js?v=8999f3cb:9083:7) at MainThreadAnimation.onKeyframesResolved (http://localhost:3333/node_modules/.sanity/vite/deps/chunk-VKDBORTS.js?v=8999f3cb:8401:36) at DOMKeyframesResolver.onResolved [as onComplete] (http://localhost:3333/node_modules/.sanity/vite/deps/chunk-VKDBORTS.js?v=8999f3cb:9067:67) at DOMKeyframesResolver.complete (http://localhost:3333/node_modules/.sanity/vite/deps/chunk-VKDBORTS.js?v=8999f3cb:8128:10) at http://localhost:3333/node_modules/.sanity/vite/deps/chunk-VKDBORTS.js?v=8999f3cb:8049:44 at Set.forEach () at measureAllKeyframes (http://localhost:3333/node_modules/.sanity/vite/deps/chunk-VKDBORTS.js?v=8999f3cb:8049:13) at flushKeyframeResolvers (http://localhost:3333/node_modules/.sanity/vite/deps/chunk-VKDBORTS.js?v=8999f3cb:8062:3) at get resolved (http://localhost:3333/node_modules/.sanity/vite/deps/chunk-VKDBORTS.js?v=8999f3cb:8378:7)

Kindly please tell me why it is happening and how I can fix it?

[evensix-dev]

Seems framer-motion introduced the behaviour of throwing an error in non production env's as of 12.4.3 for animations with too many keyframes. Until sanity fixes their keyframe use you should be able to pin the version of framer-motion to 12.4.2 via an overrides part of your package.json file (within the pnpm config if you're using that, otherwise top level)

  "overrides": {
    "framer-motion": "12.4.2"
  }

[mitchell28]

Seems framer-motion introduced the behaviour of throwing an error in non production env's as of 12.4.3 for animations with too many keyframes. Until sanity fixes their keyframe use you should be able to pin the version of framer-motion to 12.4.2 via an overrides part of your package.json file (within the pnpm config if you're using that, otherwise top level)

  "overrides": {
    "framer-motion": "12.4.2"
  }

you legend

[ngamsomset]

for someone having this issue.

follow this steps

put this is package.json (the one in root dir)

  "overrides": {
    "framer-motion": "12.4.2"
  }

• delete node_modules in root and in studio
• delete package-lock.json if it contains framer-motion that is a wrong version.
• run npm install and it should works.

I believe Sanity engineers are investigating this issue(info from their Slack chanel). this is a temporary solution.

[tomfraczek]

ok, for me it didn't work to use override. I had to use more persuasion and use:

"resolutions": {
"framer-motion": "12.4.2"
},

[vishal-prismscale]

Didn't worked for me

[vishal-prismscale]

ok, for me it didn't work to use override. I had to use more persuasion and use:

"resolutions": {
"framer-motion": "12.4.2"
},

Do we have to keep both overrides and resolutions?

[maggioniduffy]

Seems framer-motion introduced the behaviour of throwing an error in non production env's as of 12.4.3 for animations with too many keyframes. Until sanity fixes their keyframe use you should be able to pin the version of framer-motion to 12.4.2 via an overrides part of your package.json file (within the pnpm config if you're using that, otherwise top level)

  "overrides": {
    "framer-motion": "12.4.2"
  }

I love you

[SimeonGriggs]

This issue has been fixed in the 3.75.1 release

[ElizaCalmau]

ok, for me it didn't work to use override. I had to use more persuasion and use:

"resolutions": {
"framer-motion": "12.4.2"
},

worked for me, thanks

[github-actions]

This thread has been automatically locked because it has not had recent activity. Please open a new issue for related bugs and link to relevant comments in this thread.