motion.custom() is deprecated. Use motion() instead

🐛 Bug report

Provide a brief description of the bug here

This warning: motion.custom() is deprecated. Use motion() instead gets logged to the console whenever a new chakra-ui project is created with framer-motion@3.7.0. Framer motion changelog.

💥 Steps to reproduce

Clear and concise reproduction steps are important for us to be able to triage your issue in a timely manner

1. Go to ‘…’
2. Click on ‘…’
3. Scroll down to ‘…’
4. See error

💻 Link to reproduction

Please create a minimal reproduction in CodeSandbox

https://codesandbox.io/s/delicate-glitter-hroux

🧐 Expected behavior

Tell us what you expect to happen.

🧭 Possible Solution

Not compulsory, but suggesting a fix would be great!

🌍 System information

Software	Version(s)
Chakra UI
Browser
Operating System

📝 Additional information

• Screenshots or code
• Notes or link to ideas

[callum-mellorreed-privitar]

If you’re affected by this and use Yarn, for now you can add a resolution for the relevant dependency to your package.json.

"resolutions": {
  "framer-motion": "3.6.7"
}

This will tell Yarn to use framer-motion@3.6.7 even if a newer version matches the range specified by the depending package. This is the latest version before motion.custom() deprecation.

[smblee]

This breaks the chakra-cli tokens command for me.

chakra-cli tokens src/styles/theme/theme.ts