IssueRaiser

[NEXT-1151] App router issue with Framer Motion shared layout animations

### Verify canary release - [X] I verified that the issue exists in the latest Next.js canary release ### Provide environment information ```bash Operating System: Platform: linux Arch: x64 Version: #22 SMP Tue Jan 10 18:39:00 UTC 2023 Binaries: Node: 16.17.0 npm: 8.15.0 Yarn: 1.22.19 pnpm: 7.1.0 Relevant packages: next: 13.4.1-canary.1 eslint-config-next: 13.0.7 react: 18.2.0 react-dom: 18.2.0 ``` ### Which area(s) of Next.js are affected? (leave empty if unsure) App directory (appDir: true) ### Link to the code that reproduces this issue https://codesandbox.io/p/sandbox/stupefied-browser-tlwo8y?file=%2FREADME.md ### To Reproduce I provided a larger repro for context, as it is unclear which combination of factors leads to the specific bug, although a number of other people report [the same issue](https://github.com/framer/motion/issues/1850). ### Describe the Bug Framer Motion supports a feature called shared layout animation that automatically transitions components whose styles have changed when the container (that contains them) re-renders. This feature appears not to be working in multiple scenarios with Next.js 13 under the app folder. In the provided example, this feature is applied to the blue navigation highlight. The affected container in the code sandbox is: https://codesandbox.io/p/sandbox/stupefied-browser-tlwo8y?file=%2Flib%2Fcomponents%2FNavigation.tsx To produce the undes

Posted by maurocolella on May 5, 2023, 9:11 AM

Tags

Related issues

Raise real-world problems, find people facing the same issue, and discuss solutions.2,500 issues0 comments

github (SaaS)

[NEXT-1151] App router issue with Framer Motion shared layout animations

maurocolellaMay 5, 2023, 9:11 AM

### Verify canary release - [X] I verified that the issue exists in the latest Next.js canary release ### Provide environment information ```bash Operating System: Platform: linux Arch: x64 Version: #22 SMP Tue Jan 10 18:39:00 UTC 2023 Binaries: Node: 16.17.0 npm: 8.15.0 Yarn: 1.22.19 pnpm: 7.1.0 Relevant packages: next: 13.4.1-canary.1 eslint-config-next: 13.0.7 react: 18.2.0 react-dom: 18.2.0 ``` ### Which area(s) of Next.js are affected? (leave empty if unsure) App directory (appDir: true) ### Link to the code that reproduces this issue https://codesandbox.io/p/sandbox/stupefied-browser-tlwo8y?file=%2FREADME.md ### To Reproduce I provided a larger repro for context, as it is unclear which combination of factors leads to the specific bug, although a number of other people report [the same issue](https://github.com/framer/motion/issues/1850). ### Describe the Bug Framer Motion supports a feature called shared layout animation that automatically transitions components whose styles have changed when the container (that contains them) re-renders. This feature appears not to be working in multiple scenarios with Next.js 13 under the app folder. In the provided example, this feature is applied to the blue navigation highlight. The affected container in the code sandbox is: https://codesandbox.io/p/sandbox/stupefied-browser-tlwo8y?file=%2Flib%2Fcomponents%2FNavigation.tsx To produce the undes

Comments (0)

No comments yet. Start the discussion.

Comment on this issue