[BUG] Incompatible with React 19 #2668

mattgperry · 2024-05-16T08:14:54Z

Framer Motion is incompatible with React 19.

Framer itself runs on React 18 and given the scope of breaking changes (subtle and major) I think it is unlikely to be upgraded in the near-term.

To support 19, we preferably have to fix types and animations in a way that is backwards compatible with 18.

Types: #2640
Animations: #2624

Please add further examples of broken behaviour in the comments here.

rubensmit93 · 2024-05-16T09:46:15Z

Interestingly, everything does work after building, but not in dev mode (using Vite)

mattgperry · 2024-05-16T10:06:41Z

Isn't it in dev mode that React now double renders as well as runs double effects?

bryanveloso · 2024-05-16T16:05:45Z

Isn't it in dev mode that React now double renders as well as runs double effects?

From the upgrade guide, for clarity's sake:

When double rendering in Strict Mode in development, useMemo and useCallback will reuse the memoized results from the first render during the second render. Components that are already Strict Mode compatible should not notice a difference in behavior.

[...] during development, Strict Mode will double-invoke ref callback functions on initial mount, to simulate what happens when a mounted component is replaced by a Suspense fallback.

wouter173 · 2024-05-26T10:39:41Z

I have found that almost all animations break in react 19 with strict mode on. Initial state will be stuck forever and exit animations just instantly snap to the last state.

Turning off strict mode fixes all of these issues as far as I know. This is, ofcourse, inadvisable.

pixel-toys-chris-evans · 2024-05-28T09:59:40Z

Understand that from the PR this is not a priority and I've been able to work around this issue happily ^ Encountered this during a test upgrade of NextJS which is likely going to force React 19 upon it's users from 14.3.0+ (it currently throws an error at startup and asks you to upgrade to React 19.0.0 >=), so you may see more issues being raised around this particular snafu.

Just thought I'd throw it out there before the deluge of issues comes in 😂

laem · 2024-06-11T20:29:19Z

Just found this issue after searching for a while why the animations of https://github.com/Temzasse/react-modal-sheet wouldn't work in dev mode, but would in production mode. Very surprising, thanks !

motiondivision/motion#2668 (comment)

mattgperry · 2024-06-13T12:23:10Z

Track React 19 progress here: #2667

Current compatible version is framer-motion@12.0.0-alpha.0

DrewLandgraveCbsi · 2024-10-23T21:21:44Z

Track React 19 progress here: #2667

Current compatible version is framer-motion@12.0.0-alpha.0

Anyone coming here after upgrading to Next 15

It's suggested to use framer-motion@12.0.0-alpha.1 now until react 19 is out

#2667 (comment)

anonrose · 2024-10-24T04:05:53Z

@DrewLandgraveCbsi Yep!

alexwindelberg · 2024-10-24T13:02:40Z

@DrewLandgraveCbsi , This isn't working for me, I updated to the latest nextJS. Did you also update to the latest or do you have a different version?

DrewLandgraveCbsi · 2024-10-24T15:05:16Z

@alexwindelberg Do you have the proper module resolutions/overrides in your package.json?

I'm using yarn so it looks like

  "resolutions": {
    "@types/react": "npm:types-react@19.0.0-rc.1",
    "@types/react-dom": "npm:types-react-dom@19.0.0-rc.1"
  }

For npm I think it's

  "overrides": {
    "@types/react": "npm:types-react@19.0.0-rc.1",
    "@types/react-dom": "npm:types-react-dom@19.0.0-rc.1"
  }

When I ran the codemod for nextjs it did this for me

alexwindelberg · 2024-10-25T19:33:25Z

@DrewLandgraveCbsi , thank you this helped

muhaimincs · 2024-10-30T14:48:56Z

Do you guys facing any trouble for Ref?

oncet · 2024-10-31T20:02:55Z

Trying to install v12:

npm install framer-motion@v12.0.0-alpha.1
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: framer-motion@12.0.0-alpha.1
npm error Found: react@19.0.0-rc-02c0e824-20241028
npm error node_modules/react
npm error   peer react@"^18.2.0 || 19.0.0-rc-02c0e824-20241028" from next@15.0.2
npm error   node_modules/next
npm error     next@"15.0.2" from the root project
npm error   peer react@"19.0.0-rc-02c0e824-20241028" from react-dom@19.0.0-rc-02c0e824-20241028
npm error   node_modules/react-dom
npm error     peer react-dom@"^18.2.0 || 19.0.0-rc-02c0e824-20241028" from next@15.0.2
npm error     node_modules/next
npm error       next@"15.0.2" from the root project
npm error     react-dom@"19.0.0-rc-02c0e824-20241028" from the root project
npm error   2 more (styled-jsx, the root project)
npm error
npm error Could not resolve dependency:
npm error peerOptional react@"^18.0.0" from framer-motion@12.0.0-alpha.1
npm error node_modules/framer-motion
npm error   framer-motion@"v12.0.0-alpha.1" from the root project
npm error
npm error Conflicting peer dependency: react@18.3.1
npm error node_modules/react
npm error   peerOptional react@"^18.0.0" from framer-motion@12.0.0-alpha.1
npm error   node_modules/framer-motion
npm error     framer-motion@"v12.0.0-alpha.1" from the root project

Also tried with override option but I get same error:

{
  "dependencies": {
    "@types/react": "npm:types-react@rc",
    "@types/react-dom": "npm:types-react-dom@rc"
  },
  "overrides": {
    "@types/react": "npm:types-react@rc",
    "@types/react-dom": "npm:types-react-dom@rc"
  }
}

Looking at the source code, seems to still be requiring React v18:

https://github.com/framer/motion/blob/v12.0.0-alpha.1/packages/framer-motion/package.json#L84-L85

What I'm missing?

mergd · 2024-11-01T23:10:29Z

Upgrading to ^12.0.0-alpha.1 fixed issue with the LSP not recognizing the className prop

ishan0102 · 2024-11-04T04:22:35Z

Still seeing a bug where the initial opacity always remains and never transitions, but only during development. Using 12.0.0-alpha.1. Flipping reactStrictMode to false fixes it for me so I suspect there's something weird there.

oncet · 2024-11-10T00:49:11Z

Trying to install v12:

npm install framer-motion@v12.0.0-alpha.1
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: framer-motion@12.0.0-alpha.1
npm error Found: react@19.0.0-rc-02c0e824-20241028
npm error node_modules/react
npm error   peer react@"^18.2.0 || 19.0.0-rc-02c0e824-20241028" from next@15.0.2
npm error   node_modules/next
npm error     next@"15.0.2" from the root project
npm error   peer react@"19.0.0-rc-02c0e824-20241028" from react-dom@19.0.0-rc-02c0e824-20241028
npm error   node_modules/react-dom
npm error     peer react-dom@"^18.2.0 || 19.0.0-rc-02c0e824-20241028" from next@15.0.2
npm error     node_modules/next
npm error       next@"15.0.2" from the root project
npm error     react-dom@"19.0.0-rc-02c0e824-20241028" from the root project
npm error   2 more (styled-jsx, the root project)
npm error
npm error Could not resolve dependency:
npm error peerOptional react@"^18.0.0" from framer-motion@12.0.0-alpha.1
npm error node_modules/framer-motion
npm error   framer-motion@"v12.0.0-alpha.1" from the root project
npm error
npm error Conflicting peer dependency: react@18.3.1
npm error node_modules/react
npm error   peerOptional react@"^18.0.0" from framer-motion@12.0.0-alpha.1
npm error   node_modules/framer-motion
npm error     framer-motion@"v12.0.0-alpha.1" from the root project

Also tried with override option but I get same error:

{
  "dependencies": {
    "@types/react": "npm:types-react@rc",
    "@types/react-dom": "npm:types-react-dom@rc"
  },
  "overrides": {
    "@types/react": "npm:types-react@rc",
    "@types/react-dom": "npm:types-react-dom@rc"
  }
}

Looking at the source code, seems to still be requiring React v18:

https://github.com/framer/motion/blob/v12.0.0-alpha.1/packages/framer-motion/package.json#L84-L85

What I'm missing?

I did npm install framer-motion@v12.0.0-alpha.1 --force and was able to install it

I don't think it should be necessary to do force install.

longzheng · 2024-11-14T06:38:42Z

I got overrides to work with

    "dependencies": {
        "framer-motion": "^12.0.0-alpha.1",
        "next": "15.0.3",
        "react": "19.0.0-rc-66855b96-20241106",
        "react-dom": "19.0.0-rc-66855b96-20241106"
    },
    "overrides": {
        "framer-motion": {
            "react": "19.0.0-rc-66855b96-20241106",
            "react-dom": "19.0.0-rc-66855b96-20241106"
        }
    }

Then npm install will work without needing --force

ArishN · 2024-11-15T07:45:01Z

i am using next js 15 and i try to install framer motion on it but it throw error like

npm i framer-motion
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: framer-motion@11.11.17
npm error Found: react@19.0.0-rc-b01722d5-20241114
npm error node_modules/react
npm error peer react@"19.0.0-rc-b01722d5-20241114" from react-dom@19.0.0-rc-b01722d5-20241114
npm error node_modules/react-dom
npm error react-dom@"19.0.0-rc-b01722d5-20241114" from the root project
npm error peer react@"" from react-icons@5.3.0
npm error node_modules/react-icons
npm error react-icons@"^5.3.0" from the root project
npm error 2 more (styled-jsx, the root project)
npm error
npm error Could not resolve dependency:
npm error peerOptional react@"^18.0.0" from framer-motion@11.11.17
npm error node_modules/framer-motion
npm error framer-motion@"" from the root project
npm error
npm error Conflicting peer dependency: react@18.3.1
npm error node_modules/react
npm error peerOptional react@"^18.0.0" from framer-motion@11.11.17
npm error node_modules/framer-motion
npm error framer-motion@"*" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error C:\Users\Admin\AppData\Local\npm-cache_logs\2024-11-15T07_42_16_461Z-eresolve-report.txt
npm error A complete log of this run can be found in: C:\Users\Admin\AppData\Local\npm-cache_logs\2024-11-15T07_42_16_461Z-debug-0.log

when i try to downgrade my react version to 18 it works i mean it got installed is that advisable to downgrade that?

here is my dependencies in package manager :

{

"dependencies": {
"mini-svg-data-uri": "^1.4.4",
"next": "15.0.3",
"react": "19.0.0-rc-b01722d5-20241114",
"react-dom": "19.0.0-rc-b01722d5-20241114",
"react-icons": "^5.3.0"
},
}

andr3wV · 2024-11-16T00:50:42Z

I got overrides to work with

    "dependencies": {
        "framer-motion": "^12.0.0-alpha.1",
        "next": "15.0.3",
        "react": "19.0.0-rc-66855b96-20241106",
        "react-dom": "19.0.0-rc-66855b96-20241106"
    },
    "overrides": {
        "framer-motion": {
            "react": "19.0.0-rc-66855b96-20241106",
            "react-dom": "19.0.0-rc-66855b96-20241106"
        }
    }

Then npm install will work without needing --force

This is the only solution that worked for me when upgrading to Next15. Thanks!

oncet · 2024-11-16T02:37:21Z

I got overrides to work with

    "dependencies": {
        "framer-motion": "^12.0.0-alpha.1",
        "next": "15.0.3",
        "react": "19.0.0-rc-66855b96-20241106",
        "react-dom": "19.0.0-rc-66855b96-20241106"
    },
    "overrides": {
        "framer-motion": {
            "react": "19.0.0-rc-66855b96-20241106",
            "react-dom": "19.0.0-rc-66855b96-20241106"
        }
    }

Then npm install will work without needing --force

Yes, this works. But isn't framer-motion@12.0.0-alpha.1 supposed to be using React 19 already?

mohit-hexa · 2024-11-18T14:02:48Z

I m still getting the error

hexa@hexas-MacBook-Air hexa-carbon-web-fe % npm install framer-motion@v12.0.0-alpha.1

(node:63392) ExperimentalWarning: CommonJS module /opt/homebrew/lib/node_modules/npm/node_modules/debug/src/node.js is loading ES Module /opt/homebrew/lib/node_modules/npm/node_modules/supports-color/index.js using require().
Support for loading ES Module in require() is an experimental feature and might change at any time
(Use node --trace-warnings ... to show where the warning was created)
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: framer-motion@12.0.0-alpha.1
npm error Found: react@19.0.0-rc-66855b96-20241106
npm error node_modules/react
npm error peer react@"^16.8 || ^17.0 || ^18.0 || ^19.0 || ^19.0.0-rc" from @radix-ui/react-compose-refs@1.1.0
npm error node_modules/@radix-ui/react-compose-refs
npm error @radix-ui/react-compose-refs@"1.1.0" from @radix-ui/react-slot@1.1.0
npm error node_modules/@radix-ui/react-slot
npm error @radix-ui/react-slot@"^1.1.0" from the root project
npm error peer react@"^16.8 || ^17.0 || ^18.0 || ^19.0 || ^19.0.0-rc" from @radix-ui/react-slot@1.1.0
npm error node_modules/@radix-ui/react-slot
npm error @radix-ui/react-slot@"^1.1.0" from the root project
npm error 5 more (lucide-react, next, react-dom, styled-jsx, the root project)
npm error
npm error Could not resolve dependency:
npm error peerOptional react@"^18.0.0" from framer-motion@12.0.0-alpha.1
npm error node_modules/framer-motion
npm error framer-motion@"v12.0.0-alpha.1" from the root project
npm error
npm error Conflicting peer dependency: react@18.3.1
npm error node_modules/react
npm error peerOptional react@"^18.0.0" from framer-motion@12.0.0-alpha.1
npm error node_modules/framer-motion
npm error framer-motion@"v12.0.0-alpha.1" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /Users/hexa/.npm/_logs/2024-11-18T14_01_02_371Z-eresolve-report.txt
npm error A complete log of this run can be found in: /Users/hexa/.npm/_logs/2024-11-18T14_01_02_371Z-debug-0.log
hexa@hexas-MacBook-Air hexa-carbon-web-fe % npm install framer-motion@v12.0.0-alpha.1

jerrywonderr · 2024-11-22T06:19:26Z

I got overrides to work with

    "dependencies": {
        "framer-motion": "^12.0.0-alpha.1",
        "next": "15.0.3",
        "react": "19.0.0-rc-66855b96-20241106",
        "react-dom": "19.0.0-rc-66855b96-20241106"
    },
    "overrides": {
        "framer-motion": {
            "react": "19.0.0-rc-66855b96-20241106",
            "react-dom": "19.0.0-rc-66855b96-20241106"
        }
    }

Then npm install will work without needing --force

This worked for me. Thank you

FathZulfaAli · 2024-11-25T09:58:43Z

I got overrides to work with

    "dependencies": {
        "framer-motion": "^12.0.0-alpha.1",
        "next": "15.0.3",
        "react": "19.0.0-rc-66855b96-20241106",
        "react-dom": "19.0.0-rc-66855b96-20241106"
    },
    "overrides": {
        "framer-motion": {
            "react": "19.0.0-rc-66855b96-20241106",
            "react-dom": "19.0.0-rc-66855b96-20241106"
        }
    }

Then npm install will work without needing --force

For my case its work for installing but soon I use motion.div from "framer-motion" it got error

for reference my package.json

"dependencies": {
    "framer-motion": "^12.0.0-alpha.1",
    "next": "15.0.3",
    "react": "19.0.0-rc-66855b96-20241106",
    "react-dom": "19.0.0-rc-66855b96-20241106"
  },
  "devDependencies": {
    "@types/node": "^20",
    "@types/react": "^18",
    "@types/react-dom": "^18",
    "eslint": "^8",
    "eslint-config-next": "15.0.3",
    "postcss": "^8",
    "tailwindcss": "^3.4.1",
    "typescript": "^5"
  },
  "overrides": {
    "framer-motion": {
      "react": "19.0.0-rc-66855b96-20241106",
      "react-dom": "19.0.0-rc-66855b96-20241106"
     }
   }

mattgperry · 2024-11-25T10:18:27Z

FYI motion@12.0.0-alpha.2 is out now, let me know if this fixes the need for overrides.

FathZulfaAli · 2024-11-25T10:18:55Z

I got overrides to work with

    "dependencies": {
        "framer-motion": "^12.0.0-alpha.1",
        "next": "15.0.3",
        "react": "19.0.0-rc-66855b96-20241106",
        "react-dom": "19.0.0-rc-66855b96-20241106"
    },
    "overrides": {
        "framer-motion": {
            "react": "19.0.0-rc-66855b96-20241106",
            "react-dom": "19.0.0-rc-66855b96-20241106"
        }
    }

Then npm install will work without needing --force

For my case its work for installing but soon I use motion.div from "framer-motion" it got error

for reference my package.json

"dependencies": {
    "framer-motion": "^12.0.0-alpha.1",
    "next": "15.0.3",
    "react": "19.0.0-rc-66855b96-20241106",
    "react-dom": "19.0.0-rc-66855b96-20241106"
  },
  "devDependencies": {
    "@types/node": "^20",
    "@types/react": "^18",
    "@types/react-dom": "^18",
    "eslint": "^8",
    "eslint-config-next": "15.0.3",
    "postcss": "^8",
    "tailwindcss": "^3.4.1",
    "typescript": "^5"
  },
  "overrides": {
    "framer-motion": {
      "react": "19.0.0-rc-66855b96-20241106",
      "react-dom": "19.0.0-rc-66855b96-20241106"
     }
   }

My bad I've learned the "use client" is needed at the top of the file, it work thanks

Teckstudio · 2024-11-25T16:30:04Z

@FathZulfaAli THANX, had the same problem. Even though, to be fair, I could have guessed it. This should really go in the Documentation right bellow React 19 / Next 15

joevingracien · 2024-11-25T16:36:22Z

I got overrides to work with

    "dependencies": {
        "framer-motion": "^12.0.0-alpha.1",
        "next": "15.0.3",
        "react": "19.0.0-rc-66855b96-20241106",
        "react-dom": "19.0.0-rc-66855b96-20241106"
    },
    "overrides": {
        "framer-motion": {
            "react": "19.0.0-rc-66855b96-20241106",
            "react-dom": "19.0.0-rc-66855b96-20241106"
        }
    }

Then npm install will work without needing --force

For my case its work for installing but soon I use motion.div from "framer-motion" it got error

for reference my package.json

"dependencies": {
    "framer-motion": "^12.0.0-alpha.1",
    "next": "15.0.3",
    "react": "19.0.0-rc-66855b96-20241106",
    "react-dom": "19.0.0-rc-66855b96-20241106"
  },
  "devDependencies": {
    "@types/node": "^20",
    "@types/react": "^18",
    "@types/react-dom": "^18",
    "eslint": "^8",
    "eslint-config-next": "15.0.3",
    "postcss": "^8",
    "tailwindcss": "^3.4.1",
    "typescript": "^5"
  },
  "overrides": {
    "framer-motion": {
      "react": "19.0.0-rc-66855b96-20241106",
      "react-dom": "19.0.0-rc-66855b96-20241106"
     }
   }

My bad I've learned the "use client" is needed at the top of the file, it work thanks

Never tested it but, to my understanding, it appears we don't need "use client" if we use:

// React Server Components
import * as motion from "motion/client"

https://motion.dev/docs/react-motion-component#usage

longzheng · 2024-11-25T22:38:58Z

FYI motion@12.0.0-alpha.2 is out now, let me know if this fixes the need for overrides.

Confirmed working correctly without overrides.

kevod1997 · 2024-12-02T22:24:39Z

FYI motion@12.0.0-alpha.2 is out now, let me know if this fixes the need for overrides.

I did when I deployed on Vercel because it was using “npm install” during the build for installing dependencies, so I had to override it with “npm install —legacy-peer-deps“ and it worked

ArishN · 2024-12-04T04:22:19Z

FYI motion@12.0.0-alpha.2 is out now, let me know if this fixes the need for overrides.

I did when I deployed on Vercel because it was using “npm install” during the build for installing dependencies, so I had to override it with “npm install —legacy-peer-deps“ and it worked

If I am not wrong , after using “npm install —legacy-peer-deps“ you cannot install any other libraries or packages. If you try to install it will throw error.

markomitranic · 2024-12-07T17:09:10Z

I'm using react 19 due to Next 15 in a Turborepo.
Instead of doing manual overrides for each package, I've followed this advice vercel/next.js#72899 (comment) and everything except framer worked fine (althought I've had to use npm i --force).

Framer components started tossing various TS warnings due to missing types. Then I applied the 12 alpha as suggested by @ArishN above and it seems to work fine. All the TS errors are gone, and my animations still work fine so far.

spaciousejar · 2024-12-09T13:03:14Z

not compatible with React 19

6abotage · 2024-12-10T10:51:34Z

FYI motion@12.0.0-alpha.2 is out now, let me know if this fixes the need for overrides.

I tested it and it works great

"framer-motion": "^12.0.0-alpha.2", "react": "^19.0.0", "react-dom": "^19.0.0",

mattgperry · 2024-12-10T11:04:21Z

@6abotage You can try 11.13.4 too now!

dgtllion · 2024-12-10T11:53:44Z

i still get warning when install 11.13.4 with pnpm

 WARN  Issues with peer dependencies found
.
└─┬ framer-motion 11.13.4
  ├── ✕ unmet peer react@^18.0.0: found 19.0.0
  └── ✕ unmet peer react-dom@^18.0.0: found 19.0.0

mattgperry · 2024-12-10T12:02:34Z

Thanks, let me take a look with 11.13.5

mattgperry · 2024-12-10T13:24:03Z

11.13.5 should have fixed this

dgtllion · 2024-12-10T13:25:06Z

yeah now it works, Thanks a lot!

boar-is · 2024-12-10T15:06:50Z

Based on npm.js, this is related to motion package only.

mattgperry · 2024-12-10T15:11:27Z

Ah good catch, working on that now thanks

6abotage · 2024-12-11T14:13:54Z

Ah good catch, working on that now thanks

Works great, thank you for your fast work!

igorkoho · 2024-12-12T20:01:15Z

@mattgperry not sure if I've missed something, but if we want the vanilla-js version of the package, we still need to just install the "motion" package, right? I am getting the react peer deps issue as well, but react is not really part of my app -- it's just in the project for storybook.

mattgperry · 2024-12-12T20:30:18Z

@igorkoho what’s the exact error? I wonder if Storybook has an older version of React, as those deps are marked as optional so it should only fail if they’re present but don’t meet 18

igorkoho · 2024-12-12T20:57:42Z

This was the exact error. TBH I'm not even sure if I need react installed as an explicit dependency. Removing it seems to work for storybook, but I suppose I may run into some edge case where there is an issue.

# npm resolution error report

While resolving: motion@11.14.1
Found: react@16.14.0
node_modules/react
  peerOptional react@"^18.0.0 || ^19.0.0" from framer-motion@11.14.1
  node_modules/motion/node_modules/framer-motion
    framer-motion@"^11.14.1" from motion@11.14.1
    node_modules/motion
      motion@"*" from the root project

Could not resolve dependency:
peerOptional react@"^18.0.0 || ^19.0.0" from motion@11.14.1
node_modules/motion
  motion@"*" from the root project

Conflicting peer dependency: react@19.0.0
node_modules/react
  peerOptional react@"^18.0.0 || ^19.0.0" from motion@11.14.1
  node_modules/motion
    motion@"*" from the root project

Fix the upstream dependency conflict, or retry
this command with --force or --legacy-peer-deps
to accept an incorrect (and potentially broken) dependency resolution.

igorkoho · 2024-12-17T16:26:56Z

For the record, I resolved this in my project by just upgrading my storybook to v8, which doesn't require me to have react installed. Still, if there were an option to install a vanilla version of this plugin without the react peer-dep, IMO that would be great.

mattgperry · 2024-12-17T16:32:27Z

The peer dep is optional so now that Storybook doesn’t require it - it won’t be installed. It was the version mismatch that was the problem.

igorkoho · 2024-12-17T18:03:38Z

I understand, but the version of react I had installed for storybook IMO should be irrelevant for my usage of motion, which I was planning on using in vanilla JS mode. Totally understandable if keeping these packages in one install is what is needed to make shipping both more manageable, I suppose it not working in my case is an edge case.

mattgperry added the bug Something isn't working label May 16, 2024

This was referenced May 16, 2024

[BUG] react@beta (19) breaks motion's type #2640

Closed

[BUG] Elements do not animate in latest React 19 canaries #2624

Closed

React 19 #2667

Closed

ztanner mentioned this issue Jun 4, 2024

Client side navigation not working properly in latest next@rc for dev vercel/next.js#66508

Closed

laem mentioned this issue Jun 11, 2024

Incompatibility with react 19 Temzasse/react-modal-sheet#166

Closed

laem added a commit to cartesapp/cartes that referenced this issue Jun 12, 2024

Passage au mode non strict car incompatibilité framer-motion vs react 19

40101c3

motiondivision/motion#2668 (comment)

rerpha mentioned this issue Nov 6, 2024

[BUG] Can't install on NextJS 15 #2854

Open

mattgperry closed this as completed Dec 10, 2024

halvaradop mentioned this issue Dec 11, 2024

chore: update react nextjs halvaradop/tailwindcss-utilities#95

Merged

4 tasks

This was referenced Feb 17, 2025

Projects 페이지 퍼블리싱#9 2hanbyeol1/hanbyeol#10

Merged

[JOJI-845] 렌딩페이지 디자인 수정 joji-company-dev/easily-landing-page#39

Open

[BUG] Incompatible with React 19 #2668

[BUG] Incompatible with React 19 #2668

Comments

mattgperry commented May 16, 2024

rubensmit93 commented May 16, 2024

mattgperry commented May 16, 2024

bryanveloso commented May 16, 2024 • edited Loading

wouter173 commented May 26, 2024

pixel-toys-chris-evans commented May 28, 2024 • edited Loading

laem commented Jun 11, 2024

mattgperry commented Jun 13, 2024

DrewLandgraveCbsi commented Oct 23, 2024 • edited Loading

anonrose commented Oct 24, 2024

alexwindelberg commented Oct 24, 2024 • edited Loading

DrewLandgraveCbsi commented Oct 24, 2024 • edited Loading

alexwindelberg commented Oct 25, 2024

muhaimincs commented Oct 30, 2024

oncet commented Oct 31, 2024 • edited Loading

mergd commented Nov 1, 2024

ishan0102 commented Nov 4, 2024

oncet commented Nov 10, 2024

longzheng commented Nov 14, 2024 • edited Loading

ArishN commented Nov 15, 2024

andr3wV commented Nov 16, 2024 • edited Loading

oncet commented Nov 16, 2024

mohit-hexa commented Nov 18, 2024

jerrywonderr commented Nov 22, 2024

FathZulfaAli commented Nov 25, 2024

mattgperry commented Nov 25, 2024

FathZulfaAli commented Nov 25, 2024 • edited Loading

Teckstudio commented Nov 25, 2024

joevingracien commented Nov 25, 2024 • edited Loading

longzheng commented Nov 25, 2024

kevod1997 commented Dec 2, 2024

ArishN commented Dec 4, 2024

markomitranic commented Dec 7, 2024

spaciousejar commented Dec 9, 2024 • edited Loading

6abotage commented Dec 10, 2024

mattgperry commented Dec 10, 2024

dgtllion commented Dec 10, 2024

mattgperry commented Dec 10, 2024

mattgperry commented Dec 10, 2024

dgtllion commented Dec 10, 2024

boar-is commented Dec 10, 2024 • edited Loading

mattgperry commented Dec 10, 2024

6abotage commented Dec 11, 2024

igorkoho commented Dec 12, 2024

mattgperry commented Dec 12, 2024

igorkoho commented Dec 12, 2024

igorkoho commented Dec 17, 2024

mattgperry commented Dec 17, 2024

igorkoho commented Dec 17, 2024

bryanveloso commented May 16, 2024 •

edited

Loading

pixel-toys-chris-evans commented May 28, 2024 •

edited

Loading

DrewLandgraveCbsi commented Oct 23, 2024 •

edited

Loading

alexwindelberg commented Oct 24, 2024 •

edited

Loading

DrewLandgraveCbsi commented Oct 24, 2024 •

edited

Loading

oncet commented Oct 31, 2024 •

edited

Loading

longzheng commented Nov 14, 2024 •

edited

Loading

andr3wV commented Nov 16, 2024 •

edited

Loading

FathZulfaAli commented Nov 25, 2024 •

edited

Loading

joevingracien commented Nov 25, 2024 •

edited

Loading

spaciousejar commented Dec 9, 2024 •

edited

Loading

boar-is commented Dec 10, 2024 •

edited

Loading