Transition not working in NextJs
See original GitHub issueIt appears like Transition classes are not there initially on any div(<Transition>
)
Btw I’m using ( tailwindcss(^1.8.4) , styled-components & twin-macro)
Sample code I’m trying to test on my NextJs WebApp
Issue Analytics
- State:
- Created 3 years ago
- Reactions:5
- Comments:28
Top Results From Across the Web
Issues with CSS transitions on Next.js project - Stack Overflow
I'm working on a project in Next.js (React) for the first time. It's a static site (only frontend). Somehow I run into lots...
Read more >Advanced page transitions with Next.js and Framer Motion
Here's a look at how to use Next.js and Famer Motion to apply subtle, elegant page transitions that add personality and style to...
Read more >nav links with css transitions not working half the time? : r/nextjs
Basically, I am trying to do a simple css animation using transitions. The project is built in nextjs and tailwind.
Read more >Page Transition Effect in NextJS - DEV Community
I was working on page transitions using React Transition Group and the <SwitchTransition> component, with GSAP to create page transitions and ...
Read more >Page to Page loading transitions with Next.js - YouTube
GitHub : https://github.com/perkinsjr/page-to-page-loaderJoin this channel to get access to ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Here’s a working example for styled components and twin.macro: https://codesandbox.io/s/next-styled-components-tailwind-twin-starter-headless-ui-transition-forked-vow27?file=/pages/index.js
Isn’t perfect but works…
Hi, not sure if its the same issue. I just faced this a minute ago, and the solution was to hoist the classes in the inner div to the
<Transition>
initial:
After
I think this is because the <Transition> component renders the child in another div. so having your classes there might solve it.